Hi all,

Tested the following in the WSO2-IS-5.11.0-RC1.

SCIM Users endpoint

- GET/ Get User by ID
- POST/ Create User
- DELETE/ Delete User by ID
- GET/ Get Users
- POST/ Search Users
- PATCH/ Update User
- PUT/ Update User


SCIM Me Endpoint

- POST/ Create Me
- DELETE/ Delete Me
- GET/ Get Me
- PATCH/ Update Me
- PUT/ Update User

No blocking issues were found.
[+] Stable - go ahead and release

Thanks,
Hasanthi


On Tue, Nov 17, 2020 at 8:54 PM Dinika Senarath <[email protected]> wrote:
>
> Hi all,
>
> Tested the following in the WSO2-IS-5.11.0-RC1
>
> Password recovery flows (notification based/challenge question based)
> Username recovery
> SMS OTP authenticator
> TOTP authenticator
> Email/Mobile verification on update flows
> SCIM outbound provisioning (for resident SP/Oauth SPs)
> Authorization using XACML policies
>
> No blocking issues were found.
> [+] Stable - go ahead and release
>
> Regards,
> Dinika
>
> On Tue, Nov 17, 2020 at 6:13 PM Janak Amarasena <[email protected]> wrote:
>>
>> Hi All,
>>
>> Tested the following flows using a tenant with the user in JDBCUniqueId 
>> secondary userstore.
>>
>> DCR create/get/update/delete
>> Following OAuth2/OIDC grants/flows
>>
>> Authorization code
>> Authorization code with PKCE
>> Client credentials
>> Password
>> Refresh token
>> Implicit
>> OIDC hybrid flow
>>
>> No Blockers found.
>> [+] Stable - go ahead and release.
>>
>> Best Regards,
>> Janak
>>
>> On Tue, Nov 17, 2020 at 6:37 AM Isura Karunaratne <[email protected]> wrote:
>>>
>>> Hi all,
>>>
>>> Tested the following flows.
>>>
>>> Password Recovery with Email
>>> Password Recovery with Security Questions.
>>> Self User Registration.
>>> Account Locking
>>> Account Disabling.
>>> Password History validation.
>>> Password Pattern Validation.
>>>
>>> No Blockers found.
>>> [+] Stable - go ahead and release.
>>>
>>> Cheers,
>>> Isura.
>>>
>>> On Mon, Nov 16, 2020 at 10:47 PM Sathya Bandara <[email protected]> wrote:
>>>>
>>>> Hi All,
>>>>
>>>> Tested following authentication/provisioning flows.
>>>>
>>>> Federated authentication with OIDC
>>>> Inbound authentication with OIDC
>>>> Userstore Based Adaptive Authentication
>>>> TOTP Based 2 Factor Authentication
>>>> Basic SCIM2 inbound operations
>>>> Outbound provisioning with SCIM
>>>>
>>>> No Blockers found.
>>>> [+] Stable - go ahead and release.
>>>>
>>>> Thanks,
>>>> Sathya
>>>>
>>>> On Sat, Nov 14, 2020 at 6:09 PM Nipuni Paaris <[email protected]> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> We are pleased to announce the first release candidate of WSO2 Identity 
>>>>> Server 5.11.0.
>>>>>
>>>>> New Features:
>>>>>
>>>>> New react based Console application(BETA) with developer and 
>>>>> administrator views to manage and maintain the features offered by the 
>>>>> Identity Server.
>>>>>
>>>>>
>>>>> 2. Enhanced My Account application(known as User Portal in 5.10.0) for 
>>>>> users to manage their account-related preferences.
>>>>>
>>>>>
>>>>> 3. Data protection with symmetric key encryption.
>>>>> 4. User groups and roles separation and new Role Management API.
>>>>> 5. CORS management APIs.
>>>>> 6. Open SAML 3 upgrade.
>>>>>
>>>>> Fixes and Improvements:
>>>>> This release includes the following issue fixes and improvements:
>>>>>
>>>>> 5.11.0-M4
>>>>> 5.11.0-M9
>>>>> 5.11.0-M10
>>>>> 5.11.0-M11
>>>>> 5.11.0-M12
>>>>> 5.11.0-M13
>>>>> 5.11.0-M14
>>>>> 5.11.0-M15
>>>>> 5.11.0-M16
>>>>> 5.11.0-M17
>>>>> 5.11.0-M18
>>>>> 5.11.0-M19
>>>>> 5.11.0-M20
>>>>> 5.11.0-M21
>>>>> 5.11.0-M22
>>>>> 5.11.0-M23
>>>>> 5.11.0-M24
>>>>> 5.11.0-M25
>>>>> 5.11.0-M26
>>>>> 5.11.0-M27
>>>>> 5.11.0-M28
>>>>> 5.11.0-M29
>>>>> 5.11.0-M30
>>>>> 5.11.0-M32
>>>>> 5.11.0-M34
>>>>> 5.11.0-M35
>>>>> 5.11.0-Alpha
>>>>> 5.11.0-Alpha2
>>>>> 5.11.0-Alpha3
>>>>> 5.11.0-Beta
>>>>> 5.11.0-Beta2
>>>>> 5.11.0-Beta3
>>>>> 5.11.0-Beta4
>>>>> 5.11.0-Beta5
>>>>> 5.11.0-RC
>>>>>
>>>>>
>>>>> Source and Distribution
>>>>> The source and distribution are available at 
>>>>> https://github.com/wso2/product-is/releases/tag/v5.11.0-rc1
>>>>>
>>>>> Documentation
>>>>> The product documentation for this version is available at 
>>>>> https://is.docs.wso2.com/en/5.11.0
>>>>>
>>>>> Please download the product, test it, and vote using the following 
>>>>> convention.
>>>>> [+] Stable - go ahead and release
>>>>> [-] Broken - do not release (explain why)
>>>>>
>>>>> Thank you,
>>>>> WSO2 Identity and Access Management Team.
>>>>>
>>>>> Nipuni Paaris | Software Engineer | WSO2 Inc.
>>>>> (m) +94 077 9028904 | (w) +94 011 2145345 | (e): [email protected]
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Sathya Bandara
>>>> Senior Software Engineer
>>>> Blog: https://medium.com/@technospace
>>>> WSO2 Inc. http://wso2.com
>>>> Mobile: (+94) 715 360 421
>>>>
>>>> _______________________________________________
>>>> Dev mailing list
>>>> [email protected]
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>>
>>> --
>>> Isura Dilhara Karunaratne
>>> Technical Lead | WSO2
>>> lean.enterprise.middleware
>>> Email: [email protected]
>>> Mob : +94 772 254 810
>>> Blog : https://medium.com/@isurakarunaratne
>>>
>>>
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> [email protected]
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>>
>> --
>> Janak Amarasena | Senior Software Engineer | WSO2 Inc.
>> (m) +94777764144 | (w) +94112145345 | (e) [email protected]
>>
>>
>>
>> _______________________________________________
>> Iam-dev mailing list
>> [email protected]
>> http://wso2.org/cgi-bin/mailman/listinfo/iam-dev
>
>
>
> --
> Dinika Senarath
> Software Engineer | WSO2
>
> Email : [email protected]
> Mobile : +94712026357
> Blog : https://medium.com/@dinika.15
>
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev



-- 

Hasanthi Dissanayake | Associate Technical Lead | WSO2 Inc.

(m) +94718407133 | (w) +94112145345  | Email: [email protected]  |
Blog:https://medium.com/@hasanthipurnimadissanayake
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to