Newly deployed Identity Manager service fails to start on vAPP
search cancel

Newly deployed Identity Manager service fails to start on vAPP

book

Article ID: 216416

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

We are setting up a new IM, US, PS and CS in a separate Vapp cluster but our deployment failed as the IDM environment did not come up post deployment and we are receiving the following error while access IDM management console:

2021-05-04 09:13:38,265 ERROR [ims.llsdk.directory.jndi] (MSC service thread 1-10) JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "deployment.iam_im.ear.user_console.war:main" from Service Module Loader
2021-05-04 09:13:38,338 ERROR [im.provisioning.provisioningrole] (MSC service thread 1-10) Exception while obtaining JIAM session JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "deployment.iam_im.ear.user_console.war:main" from Service Module Loader
2021-05-04 09:13:38,339 ERROR [stderr] (MSC service thread 1-10) javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "deployment.iam_im.ear.user_console.war:main" from Service Module Loader [Root exception is javax.naming.AuthenticationException: [LDAP: error code 49 - :ETA_E_0302<BGU>, Bind to provisioning server as 'etaadmin' failed: Invalid credentials or Global User is locked ]]

Cause

Identity Manager is not able to connect to the Provisioning Server because it is unable to bind as the etaadmin user:

2021-05-04 09:13:38,265 ERROR [ims.llsdk.directory.jndi] (MSC service thread 1-10) JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "deployment.iam_im.ear.user_console.war:main" from Service Module Loader
2021-05-04 09:13:38,338 ERROR [im.provisioning.provisioningrole] (MSC service thread 1-10) Exception while obtaining JIAM session JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "deployment.iam_im.ear.user_console.war:main" from Service Module Loader
2021-05-04 09:13:38,339 ERROR [stderr] (MSC service thread 1-10) javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "deployment.iam_im.ear.user_console.war:main" from Service Module Loader [Root exception is javax.naming.AuthenticationException: [LDAP: error code 49 - :ETA_E_0302<BGU>, Bind to provisioning server as 'etaadmin' failed: Invalid credentials or Global User is locked ]]

 

The issue occurred because this vAPP instance was pointing to the (external) object store of another vAPP environment. This is not a supported configuration.

Each vAPP installation must have only one Identity Manager object store of its own. The Object Store cannot be shared with other vAPP systems.

Resolution

Undeploy the services, or restore fresh OVAs, and install vAPP pointing to its own databases, not that of an existing vAPP system.

Powered by Wolken Software