Previous Topic: Endpoint StructureNext Topic: Connector Objects and DNs


Distinguished Names

Distinguished names (DNs) identify the objects in a Endpoint Type. They contain a sequence of individual entries that specifies the location of an object in the DIT. That is, the DN is similar to a file system path name.

In CA IdentityMinder, the format of the DN consists of two parts: a base DN and a domain name suffix. The base DN specifies the DN of an object without any domain information. You must specify only the base DN when writing batch processes.

For example, a base DN of an Active Directory Services object is:

eTADSAccountName=my_account,eTADSContainerName=Active Dir. Folder,
eTADSDirectoryName=directory_name,
eTNamespaceName=ActiveDirectory,domain_name_suffix

The domain name suffix specifies the suffix value of the domain. This parameter is the combination of the domain name RDN, its parent domain RDNs, and the CA IdentityMinder suffix (dc=eta). You must specify the domain name suffix and the base DN when writing LDIF files. For example, if your domain name is chicago, its parent domain name is illinois, and the root domain name is usa, then the domain name suffix for your domain is:

dc=chicago,dc=illinois,dc=usa,dc=eta

Then, when accessing a logon ID using an Active Directory Services account, the DN would look like this:

eTADSAccountName=my_account,eTADSContainerName=Active Dir. Folder,
eTADSDirectoryName=directory_name,
eTNamespaceName=ActiveDirectory,dc=chicago,dc=illinois,dc=usa,dc=eta