OAM Protected Resource Request Results in "400 Bad Request" for Authenticated User After 3rd Party SSO/Application is Accessed
(Doc ID 2881325.1)
Last updated on OCTOBER 18, 2023
Applies to:
Oracle Access Manager - Version 12.2.1.1.0 and laterInformation in this document applies to any platform.
Symptoms
Users are able to authenticate successfully and access OAM protected resources without error. However, after accessing an application in the same domain or using another 3rd party authentication in the same environment during the same browser session, users receive a 400 Bad Request when accessing some or all OAM protected resources.
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 |