How can we validate password history in wso2 Identity Server 5.2.0? Is it OOTB supported or is it require custom extension?
Thanks
Roger
Password history validation is not supported OOTB in IS 5.2.0 released. It will be supported OOTB in 5.3.0 release which will be released in December 2016.
But, If you still need the password history validation for IS 5.2.0 you have to write an extension. This blog explains step by step about how to write the extension.
Thanks
Isura
Related
I am trying to utilise multitenancy feature in WSO2 by using github releases(https://github.com/wso2/product-is/releases/tag/v5.11.0). I just wanted to understand if there are any limitations for the same between enterprise version downloaded from wso2 site and github releases.
Thanks
WSO2 doesn't have an Enterprise Version of the product. Everybody uses the same base release and if you have a subscription you will be receiving product updates for bug fixes, improvements, security issues etc. Other than that there are no hidden features or limitations in the Opensource version.(Rarely some features are introduced as updates, in these cases you may not receive them) The subscription is for getting updates and getting support from WSO2.
You can read more about WSO2 subscription from here.
Adding to #YCR answer, yes, multi tenancy is supported in IS 5.11.0 and IS 6.0.0 and it was supported throughout IS 5.x series. Please see Tenant Management on WSO2 documentation.
I'm working with Identity Server 5.1, my customer requiere support multiple languages, so the login authorization page and the recovery password function on the identity server are in english by default Is there a way to manage multiple languages?
For example I want to send the recovery password email, I know the email template is in this file email-admin-config.xml and it's ok if you only support one language but in my case I need support more languages is there a way or a solution to this?
This is one of the features in the upcoming release of Identity Server (5.3.0). According to the JIRA it is available from milestone 1 release of 5.3.0. You can download the milestone releases from here.
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 there a way to inactivate a user in WSO2 identity server 5.0.0?
Inactivating should mean that the user cannot login to other applications which are SSO integrated into the IS.
Removing roles/permissions seems not to do the trick.
WSO2 IS supports account lock feature to cater your requirement from IS 4.5.0 onwards. Please follow this document.
Account disable functionality is not yet implemented and we have already reported a jira to track it in future releases.
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.