What documentation is needed when debugging a LDAP Server problem, such as connection errors, Security attribute lookup errors or password synchronization errors?

Document ID:  TEC604355
Last Modified Date:  01/09/2014
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA ACF2 for z/OS
  • CA ACF2
  • CA ACF2 Option for DB2
  • CA LDAP Server for z/OS
  • CA Web Administrator for ACF2 for z/OS
  • CA Web Administrator for Top Secret
  • CA Top Secret for z/OS

Releases

  • CA ACF2 for z/OS:Release:14
  • CA ACF2 for z/OS:Release:15
  • CA LDAP Server for z/OS:Release:15.0

Components

  • CA ACF2 for z/OS:ACF2MS
  • CA WEB ADMINISTRATOR FOR ACF2:ACFWEB
  • CA LDAP Server:LDAPDV
  • CA LDAP SERVER FOR Z/OS:TSSLDP

Description:

There is a standard list of documentation that is typically needed when debugging LDAP Server problems.

Solution:

CA LDAP Server Documentation for LDAP Problems/Issues

The following documentation and display output from Status command and ldaptest verification script will be helpful in debugging LDAP problems such as LDAP connection errors, ACF2 attribute lookup errors or password synchronization errors.

  • The display output from the CA LDAP status command, issued from the

console to show the current status of the LDAP server.

f ldapr15,status

* Note where 'ldapr15' is the LDAP Server started task name.

  • The CA LDAP Server joblog.
  • Verify the OMVS HOME directory for the LDAP started task is the same as the install directory by listing the OMVS Profile record for the id.
  • The display output from the ldaptest script to verify that the CA LDAP Server is working?
    This can be done from OMVS and switching to the CA LDAP Server installation directory as follows.

    From OMVS Change to the installation directory(for your site's install) by issuing the following command:

    cd /u/ldapr15/

    Issue ldap test command:

    syntax: ./ldaptest -u userid -w password -h host -p port
  • A copy of the slapd.conf and slapd.env file from the LDAP Server installation directory.
  • Recreate the LDAP error after turning on DEBUG and send in the stderr file. This can be done from the console as follows:

    f ldapr15,SET,DEBUG,ANY

    * Note where 'ldapr15' is the LDAP Server started task name.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >