Netscape MANAGEMENT SYSTEM 4.5 - PLUG-IN Manual page 325

Example 3
If the configured DN pattern is
CN=$attr.cn, $rdn.2, O=$dn.o, C=US
LDAP entry:
dn: UID=jdoe, OU=IS+OU=people, O=siroe.com
LDAP attributes:
LDAP attributes:
The subject name formulated will be as follows:
CN=Jane Doe, OU=IS+OU=people, O=siroe.com, C=US
the (first) '
CN= cn
second RDN in the user's entry DN.
the (first) ' ' value in the user's entry DN.
O= o
the string 'US'
C=
Example 4
If the configured DN pattern is
CN=$attr.cn, OU=$dn.ou.2+OU=$dn.ou.1, O=$dn.o, C=US
LDAP entry:
dn: UID=jdoe, OU=IS+OU=people, O=siroe, org
LDAP attributes:
LDAP attributes:
The subject name formulated will be as follows:
CN=Jane Doe, OU=people+OU=IS, O="siroe \, org", C=US
the (first) '
CN= cn
the second '
OU= ou
in the user's entry; note the multiple AVAs in a RDN in this example.
the (first) ' ' value in the user's entry DN.
O= o
the string 'US'
C=
If an attribute or subject DN component does not exist, the attribute is skipped.
cn: Jane Doe
mail: jdoe@siroe.com
' LDAP attribute value in the user's entry followed by the
cn: Jane Doe
mail: jdoe@siroe.org
' LDAP attribute value in the user's entry.
' value in the user's entry DN followed by the first '
DNs in Certificate Management System
Appendix A Distinguished Names
' value
ou
325