Hi all,

I've tested following scenarios on the IS 5.5.0-RC2 pack with PostgreSQL
database.

   - Add multiple consent purposes with multiple PII categories.
   - Enable user self-registration and self-register a new user.
   - Login to dashboard and see whether we can see the default consent and
   above added PII categories.
   - Login with the newly created user using SAML SSO and see whether we
   are getting added consents while first login and not in subsequent logins.
   - Confirm claims are getting filtered based on consents.
   - Delete the user, create another user with the exact same username, log
   in to the dashboard and see what are the consents shown.
   - Delete the SP, login to the dashboard and see whether the consents are
   deleted for that SP.
   - Tested adding custom audience values for the id token in OIDC flow.
   - Tested encrypted ID tokens in authorization code grant type, implicit
   grant type and password grant type.

+1 to go ahead with the release.

Thanks,
Vihanga.


On Thu, Mar 15, 2018 at 2:25 PM, Omindu Rathnaweera <[email protected]> wrote:

> Hi Team,
>
> Tried out the following scenarios.
>
>    - SAML SSO with a super tenant SaaS app from a tenant user
>
>
>    - Consent collection when using local claim dialect in SP configs
>       - Consent collection when using custom claim dialect in SP configs
>       - Attributes filtering in SAML response based on user consent
>       - Viewing/Updating/Revoking receipts issued by tenant user for the
>       SaaS app through self care portal
>       - Setting expiration for an issued receipt through self care portal
>       - Validating consent expiration during SSO
>
>
>    - SAML SSO with a federated IdP (Google) with email username enabled
>
>
>    - Consent collection when using local claim dialect and without
>       requested claims in SP configs (Passthrough)
>       - Consent collection when using local claim dialect and with
>       requested claims in SP configs
>
>
>    - Consent management REST APIs for super tenant and non super tenant.
>
> No blocking issue found.
>
> [+] Stable - Go ahead and release
>
> Regards,
> Omindu.
>
>
> On Thu, Mar 15, 2018 at 12:33 PM, Hasintha Indrajee <[email protected]>
> wrote:
>
>> Tested below scenarios with MySQL database
>>
>> Authentication data publishing.
>> Custom OAuth client authenticators (Private key JWT client authenticator.)
>>
>> Self registration with consents (for super and non super tenants)
>> SSO with missing mandatory claims and consents for SaaS apps. (SAML, with
>> and without mandatory claims)
>> Updating and revoking consents through dashboard for super tenant and non
>> super tenant users.
>> Consent erasure while apps (for SaaS scenarios) are deleted and users are
>> deleted.
>>
>> No blocking issues found and +1 to proceed with release.
>>
>>
>> On Thu, Mar 15, 2018 at 5:19 AM, Darshana Gunawardana <[email protected]>
>> wrote:
>>
>>> Hi all,
>>>
>>> We are pleased to announce the second release candidate of WSO2 Identity
>>> Server 5.5.0.
>>>
>>> This release fixes the following issues,
>>>
>>>    -
>>>    - 5.5.0-RC2 fixes
>>>    
>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-RC2>
>>>    - 5.5.0-RC1 fixes
>>>    
>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-RC1>
>>>    - 5.5.0-Beta fixes
>>>    
>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-beta>
>>>    - 5.5.0-Alpha3 fixes
>>>    
>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-alpha3>
>>>    - 5.5.0-Alpha2 fixes
>>>    
>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-alpha2>
>>>    - 5.5.0-Alpha fixes
>>>    
>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-alpha>
>>>    - 5.5.0-M4 fixes
>>>    
>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-M4>
>>>    - 5.5.0-M3 fixes
>>>    
>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-M3>
>>>    - 5.5.0-M2 fixes
>>>    
>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-M2>
>>>    - 5.5.0-M1 fixes
>>>    
>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-M1>
>>>
>>>
>>> Source and distribution
>>>
>>>     Runtime - https://github.com/wso2/product-is/releases/v5.5.0-rc2
>>>     Analytics - https://github.com/wso2/analytics-is/releases/v5.5.0-rc2
>>>
>>>
>>> Please download, test the product and vote.
>>>
>>>     [+] Stable - go ahead and release
>>>     [-] Broken - do not release (explain why)
>>>
>>>
>>> Thanks,
>>> - WSO2 Identity and Access Management Team -
>>>
>>> --
>>> Regards,
>>>
>>>
>>> *Darshana Gunawardana*Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>>
>>> *E-mail: [email protected] <[email protected]>*
>>> *Mobile: +94718566859 <071%20856%206859>*Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>> Hasintha Indrajee
>> WSO2, Inc.
>> Mobile:+94 771892453 <+94%2077%20189%202453>
>>
>>
>> _______________________________________________
>> Architecture mailing list
>> [email protected]
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Omindu Rathnaweera
> Senior Software Engineer, WSO2 Inc.
> Mobile: +94 771 197 211 <+94%2077%20119%207211>
>
> _______________________________________________
> Architecture mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

Vihanga Liyanage

Software Engineer | WS*O₂* Inc.

M : +*94710124103* | http://wso2.com

[image: http://wso2.com/signature] <http://wso2.com/signature>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to