LDAP-UX Client Services B.05.00 Administrator's Guide

7.3.4.5.3 Encoding of the DN
ldapuglist displays DN strings according to the encoding rules defined in RFC4514. The
escape character “\” precedes special characters, which may be the character itself or a 2 digit
hex representation of the character.
7.3.4.5.4 Passwords
In some cases, ldapuglist cannot access the user or group password fields. This can occur in
the following cases:
• The ldapuglist tool has insufficient privilege to access the password field.
• The passwords are not used to authenticate users (such as when X.500 certificates are used).
• The password is not stored in the LDAP directory server. The password might be stored in
a third-party repository such as a Kerberos Key Domain Controller.
• The password is stored in a format that cannot be parsed by HP-UX (such as {SSHA}, the
Salted Secure Hash Algorithm).
If the password is not available to ldapuglist, ldapuglist does not display the
userPassword field. If you specify the -L option, the password field will contain the “x”
character.
7.3.4.6 Specific return codes for ldapuglist
The ldapuglist tool returns a list of return codes shown in Table 7-5.
Table 7-5 Return codes for ldapuglist
MessageReturn Code
Search operation failed.
LST_SEARCH_FAILED
The <attr> parameter may not be used when the -L
option is specified.
LST_COMMANDLINE_ERR
The requested input options cannot be specified at the
same time.
LST_COMMANDLINE_ERR
The “maxcount” value must be greater than 0.LST_COMMANDLINE_ERR
The specified search base is too long.
LST_SEARCH_BASE_TOO_LONG
The specified search filter is too long.
LST_SEARCH_FILTER_TOO_LONG
The attribute mapping evaluates to an empty search filter.
For example,
ldapuglist -t passwd -f "(gecos=)"
The output of the command displays the
“LST_ATTR_MAP_EMPTY” error because the gecos values
are not specified in the command line, ldapuglist
evaluates the gecos attribute to an empty search filter.
LST_ATTR_MAP_EMPTY
One or more of the attributes specified in the search filter
is not mapped or mapped to *NULL*, cannot create search
filter. For example,
ldapuglist -t passwd -f “(userpassword=userp)”
The output of the above command displays the
“LST_ATTR_MAP_NULL” error because the
userpassword attribute is mapped to *NULL* in the
LDAP-UX configuration profile.
LST_ATTR_MAP_NULL
The attribute is not allowed when bind to the directory
server with the LDAP-UX proxy user.
LST_ATTR_NOT_ALLOWD
7.3 LDAP user and group management tools 229