Oracle Access Manager (OAM) Specific Federated Flow Fails "OAM-2 error" Instead Of Redirecting To The Landing Page
(Doc ID 2469521.1)
Last updated on AUGUST 26, 2022
Applies to:
Oracle Access Manager - Version 11.1.2.3.160719 and laterInformation in this document applies to any platform.
Symptoms
Specific Federated flow fails "OAM-2 error" instead of redirecting to the landing page.
Steps to reproduce the issue
1. Visit a protected resource and not login -This will open up the login page and will setup a webgate session for login
2. Same browser (can be a new tab) open the SAML sign in URL : https://<APPLICATION_SERVER_FQDN>/oamfed/sp/initiatesso?providerid=http://<APPLICATION2_SERVER_FQDN:NON_SSL_PORT>/oam/fed&returnurl=https://www.<SERVER_NAME_FQDN>/mypage/<SAML_SSO_APPLICATION>
3. Enter your credentials, then the fed/sso is redirecting to the APPLICATION2_SERVER_FQDN> login page with OAM-2 error instead of redirecting to the landing page.
- If ONLY Steps 2 and 3 are completed, everything works fine. But the initial step of visiting SSO protected resources first has set up a session for login and that conflicts with the SAML SSO SESSION.
Changes
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 |