VBCS User Sign Out Failing and it is not getting session to logout when using thirid part Idententiy(OKTA) with IDCS
(Doc ID 2751773.1)
Last updated on SEPTEMBER 29, 2022
Applies to:Visual Builder Studio - Version 19.4.3 and later
Information in this document applies to any platform.
VBCS app is configured Okta as a SAML IdP provider within IDCS using Okta IdP to log into the VBCS application.
Login works fine. But when we sign out of the VBCS application, it doesn't sign out. Looks like it's only signing out of the IDCS instance, and not Okta. So, when we click 'Sign Out', it gets redirected to Okta as SSO where the session is still valid, and so user gets logged in again into the VBCS app.
Steps to Reproduce:
1. Configure Okta as an IdP in IDCS and assign it to Default Sign in Policy (Pass)
2. Launch VBCS application, user is prompted with Okta Login Page (Pass)
3. Use okta credentials to sign in, and user gets into VBCS application (Pass)
4. Click 'Sign Out' link within VBCS application (Failed)
User should be logged out completely, and taken back to Idp Login page (Okta)
Log out is failing. User is not logged out of IdP (SSO). So, after clicking 'Log Out', browser redirects to IdP (Okta) where session is still valid, and then it redirects back into the IDCS/VBCS application
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document