My Oracle Support Banner

OPSS - Unable start Admin Server Error Starting Weblogic Server Having OID AuthorizationProvider, getting Invalid Credentials error (Doc ID 2403019.1)

Last updated on DECEMBER 22, 2023

Applies to:

Oracle Platform Security for Java - Version 11.1.2.3.0 and later
Information in this document applies to any platform.

Symptoms

Attempting to start the servers using the OID as Authenticator Provider, set as required, seeing the following error occurs.

weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: [LDAP: error code 49 - Invalid Credentials]
  at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)
  at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)
  at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
  at weblogic.security.SecurityService.start(SecurityService.java:141)
  at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
  Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsRuntimeException: [LDAP: error code 49 - Invalid Credentials]
  at oracle.security.jps.internal.common.ldap.connection.pool.AbstractConnectionPool.isPassingSanityConnectionTest(AbstractConnectionPool.java:152)
  at oracle.security.jps.internal.common.ldap.connection.pool.JpsJNDIConnectionPool.getInstance(JpsJNDIConnectionPool.java:68)
  at oracle.security.jps.internal.common.ldap.connection.JpsConnectionPoolManager.getPool(JpsConnectionPoolManager.java:42)
  at oracle.security.jps.internal.core.datamanager.DataManagerFactoryImpl.getLDAPDataManager(DataManagerFactoryImpl.java:173)
  at oracle.security.jps.internal.core.datamanager.DataManagerFactoryImpl.getDataManager(DataManagerFactoryImpl.java:107)
  Truncated. see log file for complete stacktrace
Caused By: javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]
  at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3087)
  at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033)
  at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2835)
  at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749)
  at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:316)
  Truncated. see log file for complete stacktrace

 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.