Hi,
How we are going to handle failure cases with this plan.
eg:
- for the monthly plan, If the subscriber has not paid or can not be
charged from the CC, Is stripe will send back the call to API M to block
that subscription?
- If the subscriber paid later, how we are going to re-activate
- When
Hi Nirubikka,
With this handler implementation, Are you planing to implement the UI for
configuring policy as we have for xacml in [1] as well?
What is the IS version we are planing add this?
[1] https://docs.wso2.com/display/IS570/Creating+a+XACML+Policy
Thanks
shammi
On Wed, May 15, 2019 at
Hi All,
Did a few basic tests covering the functionalities around OIDC, SAML and
Consent Management.
[+] Stable - go ahead and release
Thanks,
Omindu.
On Wed, May 22, 2019 at 10:17 PM Thanuja Jayasinghe
wrote:
> Hi All,
>
> Tested following scenarios,
>
> - Local user account association
> -
Hi All,
Thanks for testing WSO2 Identity Server 5.8.0-RC3.
Since this vote has passed with 20+ +1s and 0 -1s, we’re hereby closing
this vote and proceeding with the WSO2 Identity Server 5.8.0 GA release.
Best Regards,
- WSO2 Identity Server Team -
On Wed, May 22, 2019 at 10:17 PM Thanuja
Hi All,
Tested following flows and no issues found
- UMA basic flow
- OIDC hybrid flow
[+] Stable - go ahead and release.
Thanks,
Malithi
On Wed, May 22, 2019 at 9:56 PM Isura Karunaratne wrote:
> Hi all,
>
> Tested following features and no issues found.
>
>- Self User
Hi All,
I have tested the following use cases.
1. Username recovery with reCaptcha
2. Password recovery with reCaptcha
- Email
- challenge question based
3. All supported SCIM2 /Users, /Groups and /Me endpoints, tested in
primary user-store and JDBC as secondary user store.
[+] Stable -
HI All,
Tested below scenarios on IS 5.8.0-RC3 pack using MySQL 5.7 database.
- Configured secondary JDBC userstore, listed users, added users,
modified users and deleted users.
- Add service provider, configured SAML SSO, authenticate with *the
dispatch *sample web app.
- Enable
Hello everyone,
We noticed that some of the replies which were sent to this mail were not
received due to some server error.
Kindly verify whether your replies are available in archive [1] and if not
please re send the votes. Apologies for the inconvenience caused.
All the replies we have
HI All,
Following scenarios were tested
SCIM 2.0 Endpoints
1. Bulk Endpoint
- Create Users in Bulk
2. Groups Endpoint
- Create Group
- Delete Group
- Filter Groups
3. Users Endpoint
- Create User
- Delete User by ID
- Filter Users
Hi All,
Tested following scenarios,
- Local user account association
- OAuth2 grat types (code, implicit, password, client credential)
- SAML2 SSO & SLO
[+] Stable - go ahead and release.
Thanks,
Thanuja
On Wed, May 22, 2019 at 8:07 PM Farasath Ahamed wrote:
> Hi All,
>
> Test the below
Hi All,
Tested the authorization code grant flow with below configs using a native
Android client.
- PKCE enabled
- authentication without the client secret enabled
- Support PKCE 'Plain' Transform Algorithm disabled
[+] Stable - go ahead and release.
Regards,
Maduranga.
On Wed, May
Hi all,
I have tested the following functionalities
- Create a service provider using file
- SSO with SAML and OAuth app
- Role-based adaptive authentication policy
No issues found, Hence +1 to go ahead and release.
Thanks,
Senthalan
On Wed, May 22, 2019 at 8:07 PM Farasath Ahamed
Hi all,
Tested following features and no issues found.
- Self User Registration
- Password Policy
- Password History
- Password Recovery
- Account Locking
[+] Stable - go ahead and release.
Cheers,
Isura.
On Wed, May 22, 2019 at 8:07 PM Farasath Ahamed wrote:
> Hi All,
>
>
Hi All,
Resend the vote as I couldn't find my name in the archive.
Tested the following and It works fine.
- Basic functionality with EmailOTP (Basic authenticator/Federated
Authenticator as first step and EmailOTP as the second step)
- EmailOTP with Email Templates
- TOTP with basic
Hi All,
Test the below scenarios in IS 5.8.0 RC3 pack.
- Token revocation with authorization code reuse
- OIDC UserInfo with token sent in the request body and as bearer header
- OAuth Application Owner update
- Verified no username enumeration attacks possible during password
Hi All,
I have tested the following scenarios related to IS analytics and found no
issues.
- Publishing login and session events to the IS analytics server
- Analyzing login attempts
- Analyzing session statistics
- Triggering suspicious login alerts
[+] Stable - go ahead and
Hi All,
We had an issue receiving the replies to this thread and seems some of the
replies have lost due to this. Hence if you have sent a vote and it is not
available in the archive [1] please re-send the vote. All the votes we
received are positive once, so we are planing to close the vote with
Hi all,
I have tested the following and found no issues.
- CXF WS-RM Inbound Protocol
- WebSocket Inbound Protocol
+1 Stable - go ahead and release.
Thanks,
Menuka
On Wed, May 22, 2019 at 6:11 AM Thishani Lucas wrote:
> Hi all,
>
> Tested the following.
>
>- XACML authorization
Hi all,
I have tested the followings,
- Manage endpoints in Management Console and Integration Studio
- HTTP Inbound Protocol
- HTTPS Inbound Protocol
+1 Stable - Go ahead and release.
Best Regards,
Sajitha
On Wed, May 22, 2019 at 6:11 AM Thishani Lucas wrote:
> Hi all,
>
> Tested
Hi All,
I have tested following features.
1. OIDC backchannel logout
2. SAML front channel logout.
No blocking issues found.
[+] Stable - go ahead and release.
Thanks,
Hasanthi
On Wed, May 22, 2019 at 8:03 AM Isuranga Perera wrote:
> All:
> I have tested Federated Authentication
>
20 matches
Mail list logo
