My Oracle Support Banner

OCI Identity Cloud Service (IDCS) - Oracle Visual Builder (VBCS) And Fusion Application (FA) Federation Authorization Flow (Doc ID 2850338.1)

Last updated on FEBRUARY 08, 2024

Applies to:

Identity Cloud Service (IDCS) - Version N/A to N/A
Information in this document applies to any platform.

Symptoms

These VBCS Applications must be accessed from FA. The FA User must login to FA (with Azure as the IdP provider OR with IDCS as the IdP with the SAML integration on Azure) and then access the VBCS Application. The VBCS Application must open without the need for the FA User to again authenticate.

 


Problem:
The FA User must authenticate again to access the VBCS Application.
How to reproduce:
1. Clear Browser cache, close Browser, and launch Browser again.
2. Login to FA (Local Account or SSO Account).
3. Open another Browser tab and type/paste the VBCS Application URL. Instead of opening the VBCS Application, it presents a Login page to the User. Once the PaaS IDCS Identity Provider (for the specific environment) is selected, the VBCS Application then launches.

Changes

 After defining Sign-On Policies and IDP policies, while navigating from Fusion to OIC (VBCS form) the IDCS sign-in page shows up. The below triage/troubleshooting guide applies to any other PaaS application integrated to Fusion.

Note: VBCS applications sit on the Oracle Integration instance; for successful authentication and authorization the IdP Policy has to be defined with the OIC application in IDCS.

 

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.