LDAP-UX Client Services B.04.15 with Microsoft Windows Active Directory Server Administrator's Guide (edition 8)

operation (&). In the case of memberUid, each mapped attribute is used in
the search filter using the LDAP or operation (|).
In the following example, the gecos attribute has been mapped to cn, l
and telephoneNumber. If the argument to -f is “(gecos=Jane
Smith,BLD-5D,555-1212)”, then the resulting search filter presented
to the LDAP directory server is as follows:
(&(objectclass=posixAccount)(&(cn=Jane Smith)
(l=BLD-5D)(telephoneNumber=555-1212)))
As another example using memberUid, if memberUid has been mapped
to member and memberUid. If the argument to -f is
“(memberUid=jsmith)”, then the resulting search filter presented to the
LDAP directory server is:
(&(objectclass=posixGroup)(|(member= cn=Jane
Smith,ou=people,ou=myorg,dc=com) (memberUid=jsmith)))
NOTE:
• When you use -f and any of the attributes specified in the search filter
have been mapped to “*NULL*”, ldapuglist will return an error.
• Attributes that are not part of the LDAP-UX configuration profile
mapping are not modified. Refer to RFC 2307: An Approach for Using
LDAP as a Network Information Service for the list of attributes that may
be mapped.
• Do not specify -n and -f on the same command line. Doing so causes
an error.
-F <filter> Similar to -f, except that the specified <filter> is immutable. The
LDAP-UX user or group search filter defined in the configuration profile
is not amended to the specified filter, and attribute mapping does not apply
to the <filter>.
For example, the following command lists an account entry with
“(uid=EricB)”:
ldapuglist -t passwd -F "(uid=EricB)"
NOTE:
• When you use -F, the specified filter must apply to either user or group
entries and matches the -t passwd or -t group option. The
ldapuglist tool generates unpredictable results if the search filter
specified with -F discovers group entries, but the -t passwd option
was specified.
• Do not specify -n and -F on the same command line. Doing so causes
an error.
-b <base>
This option overrides the search base as defined in the LDAP-UX
configuration profile. Specifies the DN of the search base that defines where
ldapuglist starts the search in an LDAP directory server. If unspecified,
ldapuglist uses the defaultSearchBase as defined in the LDAP-UX
configuration profile.
-s <scope>
This option overrides the search scope as defined in the LDAP-UX
configuration profile. Specifies how deep in the directory tree to perform
the search. The <scope> argument can be one of the following:
178 Command, Tool, Schema Extension Utility, and Migration Script Reference