OAM Identity Asserter is not Working For Single Sign-On when Using Custom HTTP Header
(Doc ID 2348287.1)
Last updated on OCTOBER 04, 2023
Applies to:
Oracle WebLogic Server - Version 10.3.6 to 10.3.6Oracle Access Manager - Version 11.1.1.6.0 to 11.1.2.3.0 [Release 11g]
Information in this document applies to any platform.
Symptoms
OAM Identity Asserter type of Authentication Provider is included in Fusion Middleware Infrastructure install.
One can create a new authentication provider based on this type to authenticate users.
On the provider specific page for the provider, one can specify a custom header for the "SSOHeader Name" that contains user token information.
The default setting is OAM_REMOTE_USER. The OAM Identity Asserter will then validate the user token in the SSO Header by contacting Oracle Access Manager (OAM).
Although all the settings for the Identity Asserter provider are configured correctly SSO is still not working when using a custom http header specified as the "SSOHeader name".
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 |
| Cause |
| Solution |
| References |