After Configuring OAM Identity Asserter For OBIEE Application, Unable To Logon To Em Or Biacm Url
(Doc ID 2134244.1)
Last updated on SEPTEMBER 01, 2021
Applies to:Enterprise Manager for Fusion Middleware - Version 18.104.22.168.0 to 22.214.171.124.0
Information in this document applies to any platform.
Configured OAM with OBIEE.
As per the architecture, there is a load balanced OHS Servers infront of the weblogic servers and have configured them as Frontend host for our managed servers (bi server and odi server).
Everything works fine with default authentication ( Weblogic Ldap Authentication)
When "OAMIdentityAsseter" is added as the Security provider as part of OAM setup and the Whole server is restarted.
One cannot login in either of the Consoles for Fusion Middleware (em), biacm and odi.
It just stays on the login page only.
However if the "OAMIdentityAsseter" is removed as a security provider, everything works fine.
Same is if the "Webgate" Configuration is taken out from the OHS configuration everything works fine.
This happens with Admin users who are not part of OID(LDAP) like weblogic and trying to log onto biacm or em console
Weblogic user is available in embedded LDAP only. It just keeps hanging ever and does not move further.
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