OAM-OAAM-OIM integration: Error loading plugin instance for className=com.bharosa.vcrypt.services.OAAMUserMgmtOIM (Doc ID 1911715.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Adaptive Access Manager - Version 11.1.2.2.0 and later
Information in this document applies to any platform.

Symptoms

An 11.1.2.2 OAM-OIM integrated environment exists. OAAM was then added to the integration. Following this integration, users were able to enter their username and move to the password screen. However, upon submitting their password, the user is brought back to the login page with the following error being shown in the OAAM log:

 

[2014-07-22T00:41:10.154-05:00] [wls_oaam1] [ERROR] [] [oracle.oaam] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: 004zg6esYH87u1C5NFT4ie0005Co00000I,0:3] [APP: oaam_server#11.1.2.0.0] [DSID: 0000KTS__Pb6uHC5NFT4ie1JnKm100001y] [URI: /oaam_server/expiredPassword.do] Error loading plugin instance for className=com.bharosa.vcrypt.services.OAAMUserMgmtOIM[[
javax.security.auth.login.LoginException: javax.security.auth.login.LoginException: java.lang.SecurityException: User: xelsysadm, failed to be authenticated.
at weblogic.security.auth.login.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

There were no errors logged in OIM or OAM side. The following error is reported only once when the OAAM Server is restarted:

[2014-07-22T02:03:11.100-05:00] [wls_oaam1] [ERROR] [] [oracle.oaam] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: 004zgBGCJr27u1C5NFT4ie0005Co00000B,0:3] [APP: oaam_server#11.1.2.0.0] [DSID: 0000KTSsMp56uHC5NFT4ie1JnWea000006] [URI: /oaam_server/expiredPassword.do] Error loading plugin instance for className=com.bharosa.vcrypt.services.OAAMUserMgmtOIM[[
java.lang.IllegalArgumentException: No Configuration was registered that can handle the configuration named xellerate
at com.bea.common.security.jdkutils.JAASConfiguration.getAppConfigurationEntry(JAASConfiguration.java:130)
at javax.security.auth.login.LoginContext.init(LoginContext.java:243)
at javax.security.auth.login.LoginContext.(LoginContext.java:403)
at Thor.API.Security.LoginHandler.weblogicLoginHandler.login(weblogicLoginHandler.java:58)

 

After the server is started, there are no longer any occurrences of this error.

The issue is seen only for new users who's password needs to be reset. It is not noticed for users with obpasswordchange flag set to false.

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