WA dSeries (DE) and LDAP verification error

Products

• CA Workload Automation DE

Issue/Introduction

The Workload Automation dSeries (DE) is not able to connect to the LDAP / AD.

Environment

Workload Automation DE 12.x

OS: Any

Cause

The user identifier and/or LDAP url may not be correct.

 

2020XXXX 12:08:02.767 [ldap] [INFO] RMI TCP Connection(1916)-10.0.0.1: [2020-XX-XX_12:08:02.767] Creating LDAP admin context from: LdapServerConfiguration[configurationName=TEST, url=ldap://test.example.com:389, adminId=uid=user1234,ou=users,dc=test,dc=example,dc=com, SSLEnabled=false, index=1]

2020XXXX 12:08:03.066 [ldap] [ERROR] RMI TCP Connection(1916)-10.0.0.1: [2020-XX-XX_12:08:03.066] Unable to create LDAP agent with configuration: LdapServerConfiguration[configurationName=TEST, url=ldap://test.example.com:389, adminId=uid=user1234,ou=users,dc=test,dc=example,dc=com, SSLEnabled=false, index=1]

javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]

 at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3154)
 at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3100)
 at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2886)
 at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2800)
 at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319)
 at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192)
 at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210)
 at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153)
 at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
 at javax.naming.InitialContext.init(InitialContext.java:244)
 at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154)
 at com.ca.wa.core.engine.security.ldap.LdapAgent.createAdminContext(LdapAgent.java:600)
 .......

Resolution

When setting up LDAP, make sure the following (see screenshot) fields are correct.  Contact the AD or LDAP admin to get the exact user identifier and LDAP server url.

Note:  Use 'ldaps' for secure connection to LDAP server.