When a user is searched DYN endpoint it retrieving the account but many error log messages are getting created.
2019-12-04 16:14:54,152 2276115 [ApacheDS Worker-thread-55] DYNConnectorTest (JNDIAttributeStyleOpProcessor.java:189) ERROR - [LDAP: error code 32 - No Such Object]: failed to lookup o=people,o=myco,dc=test,dc=com
2019-12-04 16:14:54,153 2276116 [ApacheDS Worker-thread-55] DYNConnectorTest (AssocAttributeOpProcessorProxy.java:392) ERROR - class com.ca.jcs.jndi.JNDIMetaConnector: MyConnector [eTDYNDirectoryName=DTN,eTNamespaceName=MyConnector ,dc=im,dc=etasa]: class com.ca.jcs.assoc.AssocAttributeOpProcessorProxy: failed call on public abstract javax.naming.directory.Attributes com.ca.jcs.processor.OpProcessor.doLookUp(com.ca.jcs.ObjectInfo,java.lang.String[]) throws javax.naming.NamingException LOOKUP operation was skipped
org.apache.directory.shared.ldap.exception.LdapNameNotFoundException: JCS@T01WAP03682: JNDI: [LDAP: error code 32 - No Such Object]: failed to lookup o=people,o=myco,dc=test,dc=com
at sun.reflect.GeneratedConstructorAccessor125.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)[:1.8.0_60]
at java.lang.reflect.Constructor.newInstance(Unknown Source)[:1.8.0_60]
at com.ca.jcs.jndi.exception.JNDIExceptionToLdapMapper.mapJNDIExceptionToLdap(JNDIExceptionToLdapMapper.java:231)[131:com.ca.jcs.core:1.1.0.20180423]
at com.ca.jcs.jndi.JNDIAttributeStyleOpProcessor.handleException(JNDIAttributeStyleOpProcessor.java:192)
at com.ca.jcs.jndi.JNDIAttributeStyleOpProcessor.doLookUp(JNDIAttributeStyleOpProcessor.java:478)
at com.ca.jcs.jndi.JNDIAttributeStyleOpProcessor.doLookUp(JNDIAttributeStyleOpProcessor.java:492)
Release : 14.2
Component : IdentityMinder(Identity Manager)
ConnXP project has both the organization and organizationalUnit defined as being possible for Containers
These errors are benign and caused by the ConnXP project having both the organization and organizationalUnit defined as being possible for Containers and so the connector will try both where one is successful but the other is not hence the error.
A recommended workaround is to disable logging which is found on the acquired endpoint instance within the Provisioning Manager.