WebLogic AdminServer Fails To Start With Error: OAMAP-60513:The Identity Asserter/Authenticator did not find one or more required parameters (Doc ID 1275183.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.

Symptoms


After configuring the WebLogic Server 10.3.x default security realm with the Oracle Access Manager (OAM) Authenticator Security Provider, WebLogic Server fails to start with error:

OAMAP-60513:The Identity Asserter/Authenticator did not find one or more required parameters


The following is written to standard out during boot of WebLogic AdminServer:

....
<Dec 1, 2010 11:36:33 AM SAST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
....
<Dec 1, 2010 11:36:49 AM SAST> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: OAMAP-60513:The Identity Asserter/Authenticator did not find one or more required parameters..
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: OAMAP-60513:The Identity Asserter/Authenticator did not find one or more required parameters.
at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:342)
at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
Truncated. see log file for complete stacktrace

Caused By: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: OAMAP-60513:The Identity Asserter/Authenticator did not find one or more required parameters.
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)
Truncated. see log file for complete stacktrace
...
<Dec 1, 2010 11:36:50 AM SAST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Dec 1, 2010 11:36:50 AM SAST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>



Changes

The Oracle Access Manager Authenticator Provider was added to the WebLogic Server default 'myrealm' security realm.

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