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

LDAP-UX supports several pre-defined substitution constructs, ${<name>}, where <name>
represents:
posixProfile
Represents all RFC2307-type attributes and values for the particular name
service (either passwd or group). If LDAP-UX configuration has defined
attribute mapping for particular attributes, the mapped attributes are
substituted in its place. When you use the posixProfile construct for
posixAccount-type entries, LDAP-UX will add the following attributes and
values to the new user entry:
• cn
• uid
• userPassword
• uidNumber
• gidNumber
• gecos
• homeDirectory
• loginShell
When you use the posixProfile construct with posixGroup-type entries,
LDAP-UX will add the following attributes and values to the new group
entry:
• cn
• userPassword
• gidNumber
• memberUid
NOTE: Because use of posixProfile supports attribute mapping, if the
above attributes have been mapped as configured in the LDAP-UX
configuration profile, the mapped attributes and values are added to the
entry instead of the RFC 2307–defined attributes. For example, if the
posixAccount attribute gecos has been mapped to cn, l and
telephoneNumber then LDAP-UX adds cn, l and telephoneNumber
information to the entry instead of gecos. If the posixGroup attribute
memberUid has been mapped to uniqueMember, then LDAP-UX adds
uniqueMember information to the entry instead of memberUid.
basedn
Represents the substitution of the distinguished name of the default search
base (defaultSearchBase) as defined in the LDAP-UX configuration profile.
uid Represents the user’s account name when used in a passwd template file.
uidNumber Represents the user’s account ID number when you define it in a passwd
template file for the new user entry.
cn Represents the users’s full name when you define it in a passwd template
file. Represents the group name when you define it in a group template file.
gidNumber
Represents the group ID number when you specify it in a group template
file for the new group entry.
In addition, comments are allowed. Comments are on a separate line and the first character is
the # (hash) character.
Guidelines for Template Files
Use the following guidelines when creating template files:
• Use the first line of the template file to define the distinguished name (DN) of the new entry.
Because each DN is unique, the first component of the DN (the Relative Distinguished Name
or RDN) must be able to construct a unique value for each new entry. Define the RDN using
a ${<name>} construct. Typically, you can use the cn or uid attribute in the RDN for new
user entries and the cn attribute for new group entries.
• Define each template file for only one entry in the LDAP directory server.
196 Command, Tool, Schema Extension Utility, and Migration Script Reference