Platform Deployment Guide › Account Import › Parameter Files › User Mapping and Identification Parameters

User Mapping and Identification Parameters

/ua <LDAP attribute>

Specifies the user name attribute. Use this parameter if you need to specify a custom or non‑standard LDAP attribute.

If this parameter is omitted, CA DataMinder automatically detects the type of LDAP directory (for example, Microsoft Active Directory) and key details about the LDAP directory structure. It provides a 'best guess' when selecting the LDAP user name attribute, for example, sAMAccountName.

/fn <LDAP full name attribute>

Specifies the LDAP attribute that contains each user’s full name.

If this parameter is omitted, CA DataMinder automatically detects the type of LDAP directory (for example, Microsoft Active Directory) and provides a 'best guess' when selecting the LDAP full name attribute, for example, DisplayName.

/an <CA DataMinder account attribute>

Specifies which CA DataMinder account attribute to use as the anchor for mapping LDAP (or data file) users to CA DataMinder users. This can be the user name, the user display name, or any of the ten user attributes. Use one of these keywords:

/an username

Uses the LDAP attribute specified by the /ua parameter.

/an fullname

Uses the LDAP attribute specified by the /fn parameter.

/an attribute1

Uses the first LDAP attribute specified by the /al parameter.

/an attribute2

Uses the second LDAP attribute specified by the /al parameter.

And so on.

CA DataMinder uses the specified user attribute to locate the corresponding user in the LDAP directory.

Anchor requirements

The requirements for the CA DataMinder attribute used to anchor user import operations are as follows:

• Each user in your CA DataMinder enterprise must have a unique attribute value.
• The attribute values must not have been modified (using a conversion expression). That is, it must match exactly the corresponding attribute value in the LDAP database.
• The attribute cannot be a multiple value attribute.

/nu

When carrying out a synchronization process, it is possible that the user name in the CA DataMinder database is different to the value of the XML <user> tag or LDAP attribute used for the user name. For example, if a user has recently married.

To stop the user name in the CA DataMinder database being overwritten, add this parameter to the command line.

More information:

Importing a Single LDAP Attribute with Multiple Values