OAM Identity Assertion is Failing with Application Server 11g (Doc ID 887753.1)

Last updated on MARCH 08, 2017

Applies to:

COREid Access - Version: 10.1.4.3.0 and later   [Release: and later ]
Information in this document applies to any platform.
Checked for relevance on 13-MAY-2011

Symptoms

Oracle Access Manager (OAM) Identity Assertion is failing with Application Server 11g.

The debug WebLogic Administration Server log shows that when OAMIdentityAsserter attempts to validate the ObSSOCookie Weblogic Server gives error: BEA-000000 Failed to communicate with any of configured Access Server, ensure that it is up and running.

AdminServer.log example:

####<Sep 11, 2021 11:35:00 AM CEST> <Debug> <SecurityAtn> <weblogic2.mydomain.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue:
'weblogic.kernel.Default (self-tuning)'> <> <> <> <1631352900725> <BEA-000000> <Header Name=Cookie Value=cookiename=test;
ObSSOCookie=pOhMEPwKZsL6Vef%2FznHVC1X3CVbrdAwvp9HOqlMmvxGLyncVpn%2Fw4sAYy8Yh8cbtt2N0vthEkodtXQx%2BokVfl3fMuL0QEIShz1khCbqQmrUpkRlWJ%2BMsutULL9FdlY09E%2BbTqy5tzD0dTsEggmc8GME%2B0cnYXOBHl7mhCZrGidh6n%2B9ONETQluMpcBY5%2FqP3I1%2BvGOkKmbJXlsej3%2BtZXAdDus%2BPY2CoaOUDorQ5eGLr4hhu7J7J77FXMew5rZ1oKzKG30%2BwV0xrGeaUuuctlQ%3D%3D>
####<Sep 11, 2021 11:35:00 AM CEST> <Debug> <SecurityAtn> <weblogic2.mydomain.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue:
'weblogic.kernel.Default (self-tuning)'> <> <> <> <1631352900725> <BEA-000000> <Entering OAMUtil.validateSession>
####<Sep 11, 2021 11:35:00 AM CEST> <Debug> <SecurityAtn> <weblogic2.mydomain.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue:
'weblogic.kernel.Default (self-tuning)'> <> <> <> <1631352900729> <BEA-000000> <Validating the Cookie..>
####<Sep 11, 2021 11:35:00 AM CEST> <Error> <> <weblogic2.mydomain.com>
<AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1631352900868> <BEA-000000> <Error in receiving hashed server challenge>
####<Sep 11, 2021 11:35:00 AM CEST> <Error> <> <weblogic2.mydomain.com>
<AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default
(self-tuning)'> <> <> <> <1631352900873> <BEA-000000> <Failed to communicate with any of configured Access Server, ensure that it is up and running.>
####<Sep 11, 2021 11:35:00 AM CEST> <Error> <> <weblogic2.mydomain.com>
<AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default
(self-tuning)'> <> <> <> <1631352900873> <BEA-000000> <Failed to communicate with any of configured Access Server, ensure that it is up and running.>
####<Sep 11, 2021 11:35:00 AM CEST> <Debug> <SecurityAtn>
<weblogic2.mydomain.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue:
'weblogic.kernel.Default (self-tuning)'> <> <> <> <1631352900873> <BEA-000000> <com.bea.common.security.internal.service.IdentityAssertionTokenServiceImpl.assertIdentity - IdentityAssertionException>

 


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms