EM 13.5: SAML SSO Login Not Working and Going in a Loop, When Using The Alternate Hostname In URL
(Doc ID 3060906.1)
Last updated on DECEMBER 05, 2024
Applies to:
Enterprise Manager Base Platform - Version 13.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Successfully configured the SAML SSO on following the <Note: 2882744.1>
After providing SSO credentials, the EM Console goes in a loop and is not able to open the OMS homepage.
No significant errors in the logs:
<gc_inst>/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out
<Nov 18, 2024 2:02:06,513 PM CET> <Debug> <SecuritySAML2Atn> <BEA-000000> <DefaultSAML2NameMapperImpl: mapName: Mapped name: qualifier: null, name: <USER_ID>>
<Nov 18, 2024 2:02:06,513 PM CET> <Debug> <SecuritySAML2Atn> <BEA-000000> <SAMLIACallbackHandler: SAMLIACallbackHandler(true, A935DE, null, null)>
<Nov 18, 2024 2:02:06,513 PM CET> <Debug> <SecuritySAML2Atn> <BEA-000000> <SAMLIACallbackHandler: callback[0]: Throwing exception: Unsupported callback: weblogic.security.auth.callback.IdentityDomainUserCallback>
<Nov 18, 2024 2:02:06,513 PM CET> <Debug> <SecuritySAML2Atn> <BEA-000000> <SAMLIACallbackHandler: callback[0]: NameCallback: setName(<USER_ID>)>
<Nov 18, 2024 2:02:06,513 PM CET> <Debug> <SecuritySAML2Atn> <BEA-000000> <SAMLIACallbackHandler: callback[0]: NameCallback: setName(<USER_ID>)>
<Nov 18, 2024 2:02:06,514 PM CET> <Debug> <SecuritySAML2Atn> <BEA-000000> <SAMLIACallbackHandler: callback[0]: NameCallback: setName(<USER_ID>)>
<Nov 18, 2024 2:02:06,514 PM CET> <Debug> <SecuritySAML2Atn> <BEA-000000> <SAMLIACallbackHandler: callback[1]: Throwing exception: Unsupported callback: javax.security.auth.callback.PasswordCallback>
<Nov 18, 2024 2:02:06,514 PM CET> <Debug> <SecuritySAML2Atn> <BEA-000000> <SAMLIACallbackHandler: callback[0]: NameCallback: setName(<USER_ID>)>
<Nov 18, 2024 2:02:06,513 PM CET> <Debug> <SecuritySAML2Atn> <BEA-000000> <SAMLIACallbackHandler: SAMLIACallbackHandler(true, A935DE, null, null)>
<Nov 18, 2024 2:02:06,513 PM CET> <Debug> <SecuritySAML2Atn> <BEA-000000> <SAMLIACallbackHandler: callback[0]: Throwing exception: Unsupported callback: weblogic.security.auth.callback.IdentityDomainUserCallback>
<Nov 18, 2024 2:02:06,513 PM CET> <Debug> <SecuritySAML2Atn> <BEA-000000> <SAMLIACallbackHandler: callback[0]: NameCallback: setName(<USER_ID>)>
<Nov 18, 2024 2:02:06,513 PM CET> <Debug> <SecuritySAML2Atn> <BEA-000000> <SAMLIACallbackHandler: callback[0]: NameCallback: setName(<USER_ID>)>
<Nov 18, 2024 2:02:06,514 PM CET> <Debug> <SecuritySAML2Atn> <BEA-000000> <SAMLIACallbackHandler: callback[0]: NameCallback: setName(<USER_ID>)>
<Nov 18, 2024 2:02:06,514 PM CET> <Debug> <SecuritySAML2Atn> <BEA-000000> <SAMLIACallbackHandler: callback[1]: Throwing exception: Unsupported callback: javax.security.auth.callback.PasswordCallback>
<Nov 18, 2024 2:02:06,514 PM CET> <Debug> <SecuritySAML2Atn> <BEA-000000> <SAMLIACallbackHandler: callback[0]: NameCallback: setName(<USER_ID>)>
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 |