Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.6.1 RC2
Hi all, Tested below scenarios. - StartTLS with Read Only LDAP & Read Write LDAP User Stores. - SCIM2 GET Groups and PATCH Group (Add Member, Remove Member, Rename Group) operations on UniqueID Read Write LDAP User Store. No blocking issues found. [+] Stable - Go ahead and release Best Regards, On Tue, Nov 10, 2020 at 6:32 PM Mushthaq Rumy wrote: > Hi All, > > +1 from the API Manager Team. > > Thanks & Regards, > Mushthaq > > On Tue, Nov 10, 2020 at 6:11 PM Nadeeshani Pathirennehelage < > nadeesha...@wso2.com> wrote: > >> Hi All, >> >> +1 from the Security Team as all the security scans got completed. >> >> Best Regards, >> Nadeeshani. >> >> On Sat, Nov 7, 2020 at 3:06 PM Kanapriya Kuleswararajan < >> kanapr...@wso2.com> wrote: >> >>> Hi Devs, >>> >>> *WSO2 Carbon Kernel 4.6.1 RC2 Release Vote*. >>> >>> Please download and test your products with kernel 4.6.1 RC2 and vote. >>> The vote will be open for 72 hours or longer as needed. >>> >>> *Maven staging repository:* >>> https://maven.wso2.org/nexus/content/repositories/orgwso2carbon-4915 >>> >>> *The tag to be voted upon:* >>> https://github.com/wso2/carbon-kernel/releases/tag/v4.6.1-RC2 >>> >>> [- ] Broken - do not release (explain why) >>> [+] Stable - go ahead and release >>> >>> Thanks >>> Kanapriya Kuleswararajan >>> Senior Software Engineer >>> Mobile : - 0774894438 >>> Mail : - kanapr...@wso2.com >>> LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ >>> WSO2, Inc. >>> lean . enterprise . middleware >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >> >> >> -- >> Pathirennehelage Nadeeshani >> Senior Software Engineer >> Security & Compliance Team >> WSO2 Inc. >> mobile : +94 716545223 >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > Mushthaq Rumy > *Associate Technical Lead* > Mobile : +94 (0) 779 492140 > Email : musht...@wso2.com > WSO2, Inc.; http://wso2.com/ > lean . enterprise . middleware. > > <http://wso2.com/signature> > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Gayashan Bombuwala* Software Engineer | WSO2 Email: gayash...@wso2.com Phone: +94770548334 [image: https://wso2.com/signature] <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Identifying whether WSO2 Identity Server started up successfully
Hi all, We have the requirement to invoke some SOAP APIs in Identity Server via the command line. However, as we are starting the IS via docker as a detached process, we need to wait until the server is successfully started up before invoking any APIs. At the moment, we are looking at consuming the Carbon Health Check API[1] to identify whether the IS started up successfully without any issues. Should this be the way forward or is there a recommended alternative approach? Greatly appreciate your input on this. [1] https://is.docs.wso2.com/en/latest/setup/monitoring-server-health/ Thanks & Regards, -- *Gayashan Bombuwala* Software Engineer | WSO2 Email: gayash...@wso2.com Phone: +94770548334 [image: https://wso2.com/signature] <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Using default user attributes provided by Active Directory for SCIM operations
Hi Johann, We used to map[1] SCIM core attributes/claims like lastModifiedTIme createdTIme, scimId to some random attributes available from Active Directory such as homePostalAddress, streetAddress, pager, etc. However, Active Directory also has user attributes which are maintained by Active Directory itself such as whenChanged, whenCreated, objectGuid. Hence, we can make use of these Active Directory maintained attributes when mapping SCIM attributes/claims to AD attributes, instead of randomly mapping to some available attribute. Ex: the whenChanged attribute will be automatically updated by AD whenever we change a user attribute. See the following example mapping. CLAIM URI MAPPED ATTRIBUTE urn:scim:schemas:core:2.0:id objectGuid urn:scim:schemas:core:2.0:meta.created whenCreated urn:scim:schemas:core:2.0:meta.lastModified whenChanged However,* these Active Directory maintained user attributes are also immutable.* Hence, *we should make sure that we don't update the values of those attributes when performing SCIM operations *such when creating or updating a user. That's why we have introduced the "immutable attributes" property[2], so that we can keep track of which user store attributes should not be updated when performing SCIM operations. [1] https://docs.wso2.com/display/IS500/Provisioning+Users+to+Active+Directory+User+Store+Using+SCIM [2] https://is.docs.wso2.com/en/5.10.0/setup/configuring-a-read-write-active-directory-user-store/ Thanks, Gayashan On Wed, Mar 25, 2020 at 9:57 AM Johann Nallathamby wrote: > Hi Gayanshan, > > What is the purpose of defining the immutable attributes of Active > Directory in the "Immutable Attributes" property? How is this property used? > > Regards, > Johann. > > On Sat, Feb 1, 2020 at 11:04 PM Gayashan Bombuwala > wrote: > >> Hi Johann, Darshana, >> >> This was implemented in the product in [1]. >> In this implementation, we introduced two hooks for processing user >> attributes in the AbstarctUserStoreManager level. >> >> 1. To handle the processing of the user attributes after reading from the >> user store [2]. >> 2. To handle the processing of the user attributes before writing to the >> user store [3]. >> >> A unique ID variant [4], [5] of each of the above methods [2], [3] was >> introduced as well in order to comply with the new unique ID user store >> implementations. >> >> The behaviour of these hooks can be decided in a specific user store >> level. >> As per the implementation [1], we have implemented the behaviour of these >> hooks in UniqueIDActiveDirecotryUserStoreManager and >> ActiveDirectoryUserStoreManager [6], [7]. >> >> We have introduced two new user store properties to support the >> implementation. >> 1. Immutable Attributes >> 2. Timestamp Attributes >> >> Immutable Attributes property is used to identify the user store >> maintained immutable attributes in Active Directory such as objectGuid, >> whenChanged, whenCreated. >> Timestamp Attributes property is used to identify the attributes in >> Active Directory which belong to the "Generalized Time" data type and need >> to be converted to the standard date format before used within WSO2 iS >> (e.g. whenChanged, whenCreated). >> The usage of these two user store properties is documented in [8]. >> >> [1] https://github.com/wso2/carbon-kernel/pull/2514 >> [2] >> https://github.com/wso2/carbon-kernel/blob/b5048093ea69a24a24a71e99e62e4b1dfc412796/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/common/AbstractUserStoreManager.java#L7488 >> [3] >> https://github.com/wso2/carbon-kernel/blob/b5048093ea69a24a24a71e99e62e4b1dfc412796/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/common/AbstractUserStoreManager.java#L7500 >> [4] >> https://github.com/wso2/carbon-kernel/blob/b5048093ea69a24a24a71e99e62e4b1dfc412796/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/common/AbstractUserStoreManager.java#L7512 >> [5] >> https://github.com/wso2/carbon-kernel/blob/b5048093ea69a24a24a71e99e62e4b1dfc412796/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/common/AbstractUserStoreManager.java#L7524 >> [6] >> https://github.com/wso2/carbon-kernel/blob/b5048093ea69a24a24a71e99e62e4b1dfc412796/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/ldap/UniqueIDActiveDirectoryUserStoreManager.java#L912 >> [7] >> https://github.com/wso2/carbon-kernel/blob/b5048093ea69a24a24a71e99e62e4b1dfc412796/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/ldap/UniqueIDActiveDirectoryUserStoreManager.java#L935 >> [8] >> https://is
Re: [Dev] Using default user attributes provided by Active Directory for SCIM operations
Hi Johann, Darshana, This was implemented in the product in [1]. In this implementation, we introduced two hooks for processing user attributes in the AbstarctUserStoreManager level. 1. To handle the processing of the user attributes after reading from the user store [2]. 2. To handle the processing of the user attributes before writing to the user store [3]. A unique ID variant [4], [5] of each of the above methods [2], [3] was introduced as well in order to comply with the new unique ID user store implementations. The behaviour of these hooks can be decided in a specific user store level. As per the implementation [1], we have implemented the behaviour of these hooks in UniqueIDActiveDirecotryUserStoreManager and ActiveDirectoryUserStoreManager [6], [7]. We have introduced two new user store properties to support the implementation. 1. Immutable Attributes 2. Timestamp Attributes Immutable Attributes property is used to identify the user store maintained immutable attributes in Active Directory such as objectGuid, whenChanged, whenCreated. Timestamp Attributes property is used to identify the attributes in Active Directory which belong to the "Generalized Time" data type and need to be converted to the standard date format before used within WSO2 iS (e.g. whenChanged, whenCreated). The usage of these two user store properties is documented in [8]. [1] https://github.com/wso2/carbon-kernel/pull/2514 [2] https://github.com/wso2/carbon-kernel/blob/b5048093ea69a24a24a71e99e62e4b1dfc412796/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/common/AbstractUserStoreManager.java#L7488 [3] https://github.com/wso2/carbon-kernel/blob/b5048093ea69a24a24a71e99e62e4b1dfc412796/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/common/AbstractUserStoreManager.java#L7500 [4] https://github.com/wso2/carbon-kernel/blob/b5048093ea69a24a24a71e99e62e4b1dfc412796/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/common/AbstractUserStoreManager.java#L7512 [5] https://github.com/wso2/carbon-kernel/blob/b5048093ea69a24a24a71e99e62e4b1dfc412796/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/common/AbstractUserStoreManager.java#L7524 [6] https://github.com/wso2/carbon-kernel/blob/b5048093ea69a24a24a71e99e62e4b1dfc412796/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/ldap/UniqueIDActiveDirectoryUserStoreManager.java#L912 [7] https://github.com/wso2/carbon-kernel/blob/b5048093ea69a24a24a71e99e62e4b1dfc412796/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/ldap/UniqueIDActiveDirectoryUserStoreManager.java#L935 [8] https://is.docs.wso2.com/en/latest/setup/configuring-a-read-write-active-directory-user-store/#properties-used-in-read-write-active-directory-userstore-manager Best Regards, Gayashan On Sat, Feb 1, 2020 at 9:13 PM Darshana Gunawardana wrote: > Hi Gayashan, > > Is this implemented in the product now? If so can you share details on the > final approach you took. > > Thanks, > > On Thu, Jan 2, 2020 at 9:37 AM Johann Nallathamby wrote: > >> Hi Gayashan, >> >> On Tue, Dec 3, 2019 at 6:54 PM Gayashan Bombuwala >> wrote: >> >>> Hi all, >>> >>> Currently when managing users in Active Directory user store with SCIM, >>> we have mapped the SCIM core attributes to different attributes[1, 2] >>> supported by SCIM. >>> >>> e.g. urn:ietf:params:scim:schemas:core:2.0:id (SCIM attribute)-> >>> http://wso2.org/claims/userid (local claim) -> homePostalAddress >>> (Active Directory attribute) >>> >>> However, there are a set of attributes maintained by Active Directory >>> which we can use to map some of core SCIM attributes. We have considered >>> the following attributes for the moment. >>> >>>1. objectGuid (AD maintained attribute) -> >>>urn:ietf:params:scim:schemas:core:2.0:id (SCIM attribute) >>>2. whenCreated (AD maintained attribute) -> >>>urn:ietf:params:scim:schemas:core:2.0:created (SCIM attribute) >>>3. whenModified (AD maintained attribute)- -> >>>urn:ietf:params:scim:schemas:core:2.0:lastModified (SCIM attribute) >>> >>> We need to handle the mapping of these attributes in two scenarios. >>> >>>1. When reading values from the user store. >>>2. When writing values to the user store. >>> >>> >>> When reading from the user store we can introduce a hook to handle the >>> mapping of these special attributes. We can implement the hook in >>> AbstractUserStoreManager since local claim to user store property mapping >>> is done in that[3] level. When the attributes are mapped we may need to do >>>
[Dev] Using default user attributes provided by Active Directory for SCIM operations
Hi all, Currently when managing users in Active Directory user store with SCIM, we have mapped the SCIM core attributes to different attributes[1, 2] supported by SCIM. e.g. urn:ietf:params:scim:schemas:core:2.0:id (SCIM attribute)-> http://wso2.org/claims/userid (local claim) -> homePostalAddress (Active Directory attribute) However, there are a set of attributes maintained by Active Directory which we can use to map some of core SCIM attributes. We have considered the following attributes for the moment. 1. objectGuid (AD maintained attribute) -> urn:ietf:params:scim:schemas:core:2.0:id (SCIM attribute) 2. whenCreated (AD maintained attribute) -> urn:ietf:params:scim:schemas:core:2.0:created (SCIM attribute) 3. whenModified (AD maintained attribute)- -> urn:ietf:params:scim:schemas:core:2.0:lastModified (SCIM attribute) We need to handle the mapping of these attributes in two scenarios. 1. When reading values from the user store. 2. When writing values to the user store. When reading from the user store we can introduce a hook to handle the mapping of these special attributes. We can implement the hook in AbstractUserStoreManager since local claim to user store property mapping is done in that[3] level. When the attributes are mapped we may need to do a conversion between data types for some attributes (e.g. objectGuid property is stored in AD as an octetSting [3]). This hook will be a method with the following signature. protected void processRetrievedSpecialClaims (Map specialClaims) However, when writing values to the user store, we need to handle the special claims in the user store level [5]. We can do data type conversion for special claim values here as well if required. We will introduce an abstract hook in the AbstractUserStoreManager level but will provide separate implementations in the user store level. This hook will be a method with the following signature. protected void processSpecialClaimsForUpdating (Map specialClaims) Note that the above mentioned new behaviour will only be executed if a specific user store property is enabled. Please let us know if you have any concerns regarding this approach. Best Regards, Gayashan [1] https://docs.wso2.com/display/IS570/Configuring+Active+Directory+User+Stores+for+SCIM+2.0+based+Inbound+Provisioning [2] http://www.kouti.com/tables/userattributes.htm [3] https://docs.microsoft.com/en-us/windows/win32/adschema/s-string-octet [4] https://github.com/wso2/carbon-kernel/blob/eb6660d83a4ee29214924c5b7592fa30e259d7b5/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/common/AbstractUserStoreManager.java#L5388 [5] https://github.com/wso2/carbon-kernel/blob/eb6660d83a4ee29214924c5b7592fa30e259d7b5/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/ldap/ActiveDirectoryUserStoreManager.java#L616 -- *Gayashan Bombuwala* Software Engineer | WSO2 Email: gayash...@wso2.com Phone: +94770548334 [image: https://wso2.com/signature] <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Passing service provider object to the postDeleteHandler of the ApplicationMgtListener
Hi Johann, Both the new handler and the old handler will be called at the end[1] of deleteServiceProvider() execution. By the time that postDeleteHandler gets executed, the relevant Service Provider object will been already removed. Hence, we can't read the Service Provider object based on the name inside the postDeltedHandler. We have also deprecated[2] the old postDeleteHandler. [1] https://github.com/wso2/carbon-identity-framework/blob/07c9b78564dbd4fd652ae323d3f3ef264cf5/components/application-mgt/org.wso2.carbon.identity.application.mgt/src/main/java/org/wso2/carbon/identity/application/mgt/ApplicationManagementServiceImpl.java#L746 [2] https://github.com/wso2/carbon-identity-framework/blob/07c9b78564dbd4fd652ae323d3f3ef264cf5/components/application-mgt/org.wso2.carbon.identity.application.mgt/src/main/java/org/wso2/carbon/identity/application/mgt/listener/ApplicationMgtListener.java#L121 Regards, Gayashan. On Fri, Nov 1, 2019 at 3:37 PM Johann Nallathamby wrote: > Hi Gayashan, > > Though you introduce the method in the API, who calls the method? Now that > there are two methods is the ApplicationMgtService going to call both the > methods? Can't we read the Service Provider object based on the name rather > than introducing a new method for it? > > Regards, > Johann. > > On Fri, Oct 25, 2019 at 4:45 PM Gayashan Bombuwala > wrote: > >> Hi all, >> >> Currently implementation of the postDeleteHandler[1] of >> ApplicationMgtListener only accepts the name of the service provider as a >> parameter. However the postCreateHandler[2] and postUpdateHandler[3] of the >> ApplicationMgtListener accepts the relevant Service Provider object as a >> parameter rather than just the service provider name.We will be introducing >> a new overloaded postDeleteHandler to the ApplicationMgtListener interface >> where the relevant Service Provider object get passed to the handler >> similar to the postCreateHandler[2] and postUpdateHandler[3] as the >> relevant Service Provider information is required for logging purposes. >> >> [1] >> https://github.com/wso2/carbon-identity-framework/blob/b95514a65960e75015855d343ebd9452c4ce6a2b/components/application-mgt/org.wso2.carbon.identity.application.mgt/src/main/java/org/wso2/carbon/identity/application/mgt/listener/ApplicationMgtListener.java#L117 >> >> [2] >> https://github.com/wso2/carbon-identity-framework/blob/b95514a65960e75015855d343ebd9452c4ce6a2b/components/application-mgt/org.wso2.carbon.identity.application.mgt/src/main/java/org/wso2/carbon/identity/application/mgt/listener/ApplicationMgtListener.java#L69 >> >> [3] >> https://github.com/wso2/carbon-identity-framework/blob/b95514a65960e75015855d343ebd9452c4ce6a2b/components/application-mgt/org.wso2.carbon.identity.application.mgt/src/main/java/org/wso2/carbon/identity/application/mgt/listener/ApplicationMgtListener.java#L93 >> >> Thanks, >> -- >> *Gayashan Bombuwala* >> Software Engineer | WSO2 >> >> Email: gayash...@wso2.com >> Phone: +94770548334 >> >> [image: https://wso2.com/signature] <https://wso2.com/signature> >> > > > -- > *Johann Dilantha Nallathamby* | Associate Director/Solutions Architect | > WSO2 Inc. > (m) +94 (77) 7776950 | (w) +94 (11) 2145345 | (e) joh...@wso2.com > [image: Signature.jpg] > -- *Gayashan Bombuwala* Software Engineer | WSO2 Email: gayash...@wso2.com Phone: +94770548334 [image: https://wso2.com/signature] <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Passing service provider object to the postDeleteHandler of the ApplicationMgtListener
Hi all, Currently implementation of the postDeleteHandler[1] of ApplicationMgtListener only accepts the name of the service provider as a parameter. However the postCreateHandler[2] and postUpdateHandler[3] of the ApplicationMgtListener accepts the relevant Service Provider object as a parameter rather than just the service provider name.We will be introducing a new overloaded postDeleteHandler to the ApplicationMgtListener interface where the relevant Service Provider object get passed to the handler similar to the postCreateHandler[2] and postUpdateHandler[3] as the relevant Service Provider information is required for logging purposes. [1] https://github.com/wso2/carbon-identity-framework/blob/b95514a65960e75015855d343ebd9452c4ce6a2b/components/application-mgt/org.wso2.carbon.identity.application.mgt/src/main/java/org/wso2/carbon/identity/application/mgt/listener/ApplicationMgtListener.java#L117 [2] https://github.com/wso2/carbon-identity-framework/blob/b95514a65960e75015855d343ebd9452c4ce6a2b/components/application-mgt/org.wso2.carbon.identity.application.mgt/src/main/java/org/wso2/carbon/identity/application/mgt/listener/ApplicationMgtListener.java#L69 [3] https://github.com/wso2/carbon-identity-framework/blob/b95514a65960e75015855d343ebd9452c4ce6a2b/components/application-mgt/org.wso2.carbon.identity.application.mgt/src/main/java/org/wso2/carbon/identity/application/mgt/listener/ApplicationMgtListener.java#L93 Thanks, -- *Gayashan Bombuwala* Software Engineer | WSO2 Email: gayash...@wso2.com Phone: +94770548334 [image: https://wso2.com/signature] <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Removing assertion expiry time check when setting the "exp" claim in a new JWT token
Hi all, Currently, when issuing a JWT token in exchange for a password grant assertion, we do the comparison [1]. When setting the "exp" claim, we check whether the expiration time of the assertion is earlier than the expiration time defined by the service provider. If that is the case, we set the "exp" claim of the new token to expiration time of the assertion. The reason for doing this comparison is because when an IDP issue a password grant, the IDP trusts that the original validity period will be preserved when the Identity Server issue a new token in exchange of the password grant assertion. Based on the discussion we had offline, we decided to refactor the code where the above mentioned logic will not be carried out. [1] https://github.com/wso2-extensions/identity-inbound-auth-oauth/blob/ac03fc9eeff9b183430963c5590753bd7d245e23/components/org.wso2.carbon.identity.oauth/src/main/java/org/wso2/carbon/identity/oauth2/token/JWTTokenIssuer.java#L524 Best Regards, -- *Gayashan Bombuwala* Software Engineer | WSO2 Email: gayash...@wso2.com Phone: +94770548334 [image: https://wso2.com/signature] <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Identity Server 5.9.0 RC2
nge questions answers >>>>>> >>>>>>Authorized OAuth Apps - List and revoke >>>>>> >>>>>>User session management >>>>>> >>>>>>Pending Approvals >>>>>> >>>>>> >>>>>> +1 to proceed. >>>>>> >>>>>> On Wed, Oct 2, 2019 at 4:26 PM Buddhima Udaranga >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> We have tested the Configuration Management REST API with the WSO2 >>>>>>> IS 5.9.0-RC2 with the MySQL database. No blocker issues found. +1 to >>>>>>> proceed. >>>>>>> >>>>>>> Thanks, >>>>>>> *Buddhima Udaranga*|Software Engineer| WSO2 Inc. <http://wso2.com/> >>>>>>> (M)+94 714742094 | (E) buddhi...@wso2.com >>>>>>> <https://wso2.com/signature> >>>>>>> >>>>>>> >>>>>>> On Wed, Oct 2, 2019 at 10:59 AM Piraveena Paralogarajah < >>>>>>> pirave...@wso2.com> wrote: >>>>>>> >>>>>>>> Hi all, >>>>>>>> >>>>>>>> >>>>>>>> We are pleased to announce the second release candidate of WSO2 >>>>>>>> Identity Server 5.9.0. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> New Features >>>>>>>> >>>>>>>>- >>>>>>>> >>>>>>>>An improved, simpler configuration model >>>>>>>>- >>>>>>>> >>>>>>>>RESTful APIs for user self-services >>>>>>>>- >>>>>>>> >>>>>>>>Passwordless authentication with WebAuthn >>>>>>>>- >>>>>>>> >>>>>>>>Reusable script library for adaptive authentication >>>>>>>>- >>>>>>>> >>>>>>>>Cross-protocol single logout capability >>>>>>>>- >>>>>>>> >>>>>>>>Inbuilt support to view and revoke user sessions >>>>>>>>- >>>>>>>> >>>>>>>>Azure AD/Office365 multi-domain federation support >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Fixes >>>>>>>> >>>>>>>> This release includes the following issue fixes and improvements: >>>>>>>> >>>>>>>>- >>>>>>>> >>>>>>>>5.9.0-m1 >>>>>>>><https://github.com/wso2/product-is/milestone/85?closed=1> >>>>>>>>- >>>>>>>> >>>>>>>>5.9.0-m2 >>>>>>>><https://github.com/wso2/product-is/milestone/86?closed=1> >>>>>>>>- >>>>>>>> >>>>>>>>5.9.0-m3 >>>>>>>><https://github.com/wso2/product-is/milestone/87?closed=1> >>>>>>>>- >>>>>>>> >>>>>>>>5.9.0-m4 >>>>>>>><https://github.com/wso2/product-is/milestone/88?closed=1> >>>>>>>>- >>>>>>>> >>>>>>>>5.9.0-m5 >>>>>>>><https://github.com/wso2/product-is/milestone/90?closed=1> >>>>>>>>- >>>>>>>> >>>>>>>>5.9.0-m6 >>>>>>>><https://github.com/wso2/product-is/milestone/91?closed=1> >>>>>>>>- >>>>>>>> >>>>>>>>5.9.0-alpha >>>>>>>><https://github.com/wso2/product-is/milestone/89?closed=1> >>>>>>>>- >>>>>>>> >>>>>>>>5.9.0-beta >>>>>>>><https://github.com/wso2/product-is/milestone/93?closed=1> >>>>>>>>- >>>>>>>> >>>>>>>>5.9.0-GA >>>>>>>><https://github.com/wso2/product-is/milestone/83?closed=1> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Source and Distribution >>>>>>>> >>>>>>>> The source and distribution >>>>>>>> <https://github.com/wso2/product-is/releases/download/v5.9.0-rc2/wso2is-5.9.0-rc2.zip> >>>>>>>> are available at >>>>>>>> https://github.com/wso2/product-is/releases/tag/v5.9.0-rc2 >>>>>>>> >>>>>>>> >>>>>>>> Please download the product, test it, and vote using the following >>>>>>>> convention. >>>>>>>> >>>>>>>> [+] Stable - go ahead and release >>>>>>>> >>>>>>>> [-] Broken - do not release (explain why) >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> WSO2 Identity and Access Management Team >>>>>>>> >>>>>>>> *Piraveena Paralogarajah* >>>>>>>> Software Engineer | WSO2 Inc. >>>>>>>> *(m)* +94776099594 | *(e)* pirave...@wso2.com >>>>>>>> >>>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Niluka Sripali Monnankulama >>>>>> Software Engineer - WSO2 Sri Lanka >>>>>> >>>>>> Mobile : +94 76 76 52843 >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> *Mathuriga Thavarajah* >>>>> Software Engineer >>>>> WSO2 Inc. - http ://wso2.com >>>>> >>>>> Email : mathur...@wso2.com >>>>> Mobile : +94778191300 >>>>> >>>>> >>>>> >>>>> *[image: http://wso2.com/signature] <http://wso2.com/signature>* >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>> >>> >>> -- >>> *Shanika Wickramasinghe* >>> Software Engineer - QA Team >>> >>> Email: shani...@wso2.com >>> Mobile : +94713503563 >>> Web : http://wso2.com >>> >>> <http://wso2.com/signature> >>> >> >> >> -- >> Ashen Weerathunga | Senior Software Engineer | WSO2 Inc. >> (m) +94716042995 | (w) +94112145345 | Email: as...@wso2.com >> <http://wso2.com/signature> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > > Vihanga Liyanage > > Software Engineer | WS*O₂* Inc. > > M : +*94710124103* | http://wso2.com > > [image: http://wso2.com/signature] <http://wso2.com/signature> > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Gayashan Bombuwala* Software Engineer | WSO2 Email: gayash...@wso2.com Phone: +94770548334 [image: https://wso2.com/signature] <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
