I have an issue with the Last Access time statistics, its give me a wrong date.
Regards.
This was indeed a bug in WSO2 API-M 1.1.0 which was present in Firefox browser. This has been reported in WSO2 API-M Jira and has been fixed.
The fix is in version 2.0.0 and you can download the pack from here. Please note that as of this moment it is in beta version.
Related
I am trying to install following feature in wso2 API manager 2.0.
http://xacmlinfo.org/2015/05/13/federated-authenticators-in-wso2-api-manager-wso2apim/
but I am getting error in API manager's console while installations.
It seems the above package is not compatible for 2.0 version.
Please suggest me the exact version of 'Application Authenticator' feature which is compatible with wso2 AM version 2.0.
Thanks in advance
It seems the p2 repos are still not updated with the latest Authenticator versions based on Identity Application Management Server Feature 5.2.0 or above. This will be updated soon with the next release.
However you can use WSO2 IS for this use case. You can configure SSO for APIM with IS using this link . Then you can federate IS for OpenAM with this link . With that you can connect APIM with openAM.
Hope this helps.
Is Latest Version of WSO2 API Manager(2.0.0) compatible with latest version of WSO DAS(3.1.0)?
In the download page of WSO2 API Manager 2.0.0, only WSO DAS 2.0.0 download is mentioned for Analytics.
Yes, they are compatible.
2nd question is not much clear. Could you please tell where it says about DAS 2.0.0? Actually, there is no version 2.0.0 in DAS. It was called BAM before.
If you're talking about wso2am-analytics-2.0.0.zip pack, it's a customized version of DAS 3.0.x. It has required CAR files installed and is configured to work with APIM, with less manual configurations.
Kinda new to WSO products. Installed WSO DSS 3.5.0 and created a simple test data service following all the instructions on WSO documentation. it is working fine except I can not find out how to implement the security for data service as mentioned in the documentation :
https://docs.wso2.com/display/DSS350/Filtering+Content+to+Specific+User+Roles
The problem is that Quality Of Service Configuration Panel is empty in my web console and no menu exists there for security or anything else except the edit data service menu as you can see :
Spending a full day reading docs searching googling etc for the solution I have not found any..
Anyone else facing this same issue? should I activate it in features somehow or is there another product needed to be installed together with DSS for this to work?
WSO2 DSS 3.5.0 is carbon kernel 4.4.x based product. From kernel 4.4.x on wards QoS features are removed from the kernel.
You have to use WSO2 Developer Studio to implemnet QoS for the requirement.
I am trying to register WSO2 as a identity provider for PingOne. After configuring both PingOne and WSO2 PingOne would complain about not being able to process WSO2's SAML response.
After working with Ping technical support, we discovered that the WSO2 compresses SAML when sending it using the SAML POST binding which is a violation of the SAML specification.
I dug around on the web and it seems that the WSO2 team is already aware of this issue and it is fixed in version 4.1.1. Unfortunately, there does not seem to be a 4.1.1 download on the WSO2 page.
If the WSO2 support team monitoring stack overflow could please recommend how I should proceed to work around this issue I would greatly appreciate it.
There was such issue and it has been fixed in 4.5.0. Actually, there was a plan to release 4.1.1. But due to new features, finally it has been renamed as 4.5.0. Please download 4.5.0 from official website http://wso2.com/products/identity-server and try out it.
We have discovered a major issue with WSO2 API Manager 1.3 and it's integration into the WSO2 BAM 2.0.1 analytics product and I'm wondering if anyone out there has worked around this issue?
Details
After 100 calls trying to log API data to the BAM server all further calls will fail and in some cases this will stop the API Manager server from service API requests also.
The problem occurs in the DataPublisher.java class that acquires a permit from one semaphore and then releases the permit on the wrong semaphore.
Mentioned in the JIRA issue at https://wso2.org/jira/browse/APIMANAGER-992
This is obviously a blocker for us in using API Manager as we can no longer show clients any API analytics - hoping someone out there has had a similar problem and fingers crossed a work around.
We have done some major improvements to API Manager's Data publisher. These fixes will be included in 1.4.0 release, which will be ready by end of April.
We are planning to push preview releases from this week on wards. I am not particularly sure if the mentioned issue is fixed by now. However We have made this a blocker for 1.4.0 release. Hence, if not fixed by now it will be taken up soon. We will be updating the JIRA issue with progress.