AD- IDCS - Primavera (user sync) is causing SSO via SAML Okta not to work for some users
(Doc ID 2789544.1)
Last updated on MARCH 30, 2023
Applies to:
Identity Cloud Service (IDCS) - Version N/A to N/AInformation in this document applies to any platform.
Symptoms
Users unable to log in via existing SAML SSO between IDCS and Okta due to AD sync creating a second user due to a discrepancy of usernames.
e.g:
jdoe (Primavera - IDCS existing user)
johndoe (AD - IDCS - Primavera sync) => this user doesn't get passed the Company attribute in Primavera and is causing SSO (SAML IDCS-OKTA) to show an error when logging in.
Changes
AD sync via identity bridge caused login issues for some users due duplicate creation and due to required Primavera missing field (Company). We're yet to determine what are the necessary attributes that need to flow from AD through IDCS and into Primavera.
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 |