WSO2 Identity Server 5.1.0 Milestone 5 Released! Date: 31st July 2015The WSO2 Identity Server team is pleased to announce the 5th Milestone of WSO2 Identity Server 5.1.0. You can download this distribution from https://github.com/wso2/product-is/releases/tag/v5.1.0-m5
Following list [1] contains all bug fixes and improvements available with this milestone. We encourage you to report issues, improvements and feature requests regarding WSO2 Identity Server through the public WSO2 Identity Server JIRA <https://wso2.org/jira/browse/IDENTITY> ~ The WSO2 Identity Server Team ~ [1] Release Notes - WSO2 Identity Server - Version 5.1.0-M5 Bug - [IDENTITY-3011 <https://wso2.org/jira/browse/IDENTITY-3011>] - Log statement not included in Carbon Context refactoring - [IDENTITY-3319 <https://wso2.org/jira/browse/IDENTITY-3319>] - NPE thrown when session timeouts when SSO is enabled. - [IDENTITY-3397 <https://wso2.org/jira/browse/IDENTITY-3397>] - Exceptions while logging in using IWA authenticator - [IDENTITY-3439 <https://wso2.org/jira/browse/IDENTITY-3439>] - No exception was throwing from IS server when gives a wrong access token in Oauth2 - [IDENTITY-3442 <https://wso2.org/jira/browse/IDENTITY-3442>] - -Dsetup doesn't work on MSSQL - [IDENTITY-3452 <https://wso2.org/jira/browse/IDENTITY-3452>] - Claims map need to be cloned before passing to user store for setUserClaims in UserStoreBasedIdentityDataStore. - [IDENTITY-3453 <https://wso2.org/jira/browse/IDENTITY-3453>] - Admin account unlock doesnt work when JDBCIdentityDataStore is used Improvement - [IDENTITY-1837 <https://wso2.org/jira/browse/IDENTITY-1837>] - SAML2 SSO Authenticator should have facility to specify the IdP SLO URL - [IDENTITY-3413 <https://wso2.org/jira/browse/IDENTITY-3413>] - Split AUTHZ_USER column of IDN_OAUTH2_ACCESS_TOKEN table into USER_DOMAIN and AUTHZ_USER - [IDENTITY-3443 <https://wso2.org/jira/browse/IDENTITY-3443>] - SAML1.0 OAuth bearer grant type support - [IDENTITY-3451 <https://wso2.org/jira/browse/IDENTITY-3451>] - User store based Identity data store is coupled with existing user stores. Make it independent of the type of user store New Feature - [IDENTITY-3393 <https://wso2.org/jira/browse/IDENTITY-3393>] - Workflow framework for IS Patch - [IDENTITY-2663 <https://wso2.org/jira/browse/IDENTITY-2663>] - Carbon Management console UI does not check session validity before initialized the logout. - [IDENTITY-3409 <https://wso2.org/jira/browse/IDENTITY-3409>] - Access Tokens are not revoked, if user is deleted from secondary user store - [IDENTITY-3411 <https://wso2.org/jira/browse/IDENTITY-3411>] - Some of the session attributes are not persisted at SSOSessionPersistenceManager - [IDENTITY-3412 <https://wso2.org/jira/browse/IDENTITY-3412>] - SAML response is always signed with super tenant's key - [IDENTITY-3421 <https://wso2.org/jira/browse/IDENTITY-3421>] - Claim values that are posted back from WSO2 passivests are not HTML encoded - [IDENTITY-3431 <https://wso2.org/jira/browse/IDENTITY-3431>] - Social Account Association does not work properly for tenant users. - [IDENTITY-3468 <https://wso2.org/jira/browse/IDENTITY-3468>] - Policy versions not ordered and default most recent version is incorrect Task - [IDENTITY-3471 <https://wso2.org/jira/browse/IDENTITY-3471>] - Move "Users & Roles" , "User Store Management" and "Claim Management" under "Identity" sub menu Sub-task - [IDENTITY-2660 <https://wso2.org/jira/browse/IDENTITY-2660>] - Admin user account getting locked out due to incorrect password attempts -- Hasintha Indrajee Software Engineer WSO2, Inc. Mobile:+94 771892453
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
