Configuring User Accounts › Special Handling Types › How CA SDM Uses LDAP Data to Communicate › Troubleshooting › Test Connections to LDAP Directories › Monitor LDAP Using Trace Logging › Determine Which LDAP Data is Available and Not Available

Determine Which LDAP Data is Available and Not Available

Assuming that CA SDM was able to map to the LDAP object’s ID attribute successfully, the attributes as defined in $NX_ROOT/bopcfg/majic/ldap.maj are retrieved for each entry, or a message is logged indicating that an attribute has not been defined. A sample of these messages is as follows:

06/24 14:18:28.41 mclda04- bopLDAP       3844 TRACE   ldap_virtdb.c   1396 Value not available for 'modifyTimestamp‘

06/24 14:18:28.41 mclda04- bopLDAP       3844 TRACE   ldap_virtdb.c   1396 Value not available for 'telephoneNumber,pzWorkPhoneNumber'