Mapping LDAP and Liberty Attributes

You can create an LDAP attribute map or edit an existing one. To create an attribute map, you specify how single-value and multi-value data items map to single-value and multi-value LDAP attributes. A single-value attribute can contain no more than one value, and a multi-value attribute can contain more than one. An example of a single-value attribute might be a person’s gender, and an example of a multi-value attribute might be a person’s various e-mail addresses, phone numbers, or titles.

  1. Click Devices> Identity Servers > Edit > Liberty >LDAP Attribute Mapping.

  2. Select one of the following actions:

    New: Allows you create an LDAP attribute mapping. Select from the following types:

    Delete: Deletes the selected mapping.

    Enable: Enables the selected mapping.

    Disable: Disables the selected mapping. When the mapping is disabled, the server does not load the definition. However, the definition is not deleted.

  3. Click OK, then update Identity Server.

Configuring One-to-One Attribute Maps

A one-to-one map enables you to map single-value and multiple-value LDAP attribute names to standard Liberty attributes. A default one-to-one attribute map is provided with Access Manager, but you can also define your own.

An example of a one-to-one attribute map might be the single-valued Liberty attribute Common Name (CommonName) used by the Personal Profile that is mapped to the LDAP attribute givenName. You can further configure the various Liberty values to map to any LDAP attribute names that you use.

  1. Click Devices > Identity Servers > Edit > Liberty > LDAP Attribute Mapping > New > One to One.

  2. Specify the following details:

    Type: Displays the type of mapping you are modifying or creating:

    Name: The name you want to give the map.

    Description: A description of the map.

    Access Rights: If you set this to Read/Write, you can specify rights for individual data items.

    For user provisioning to succeed, you must select Read/Write for any maps that use an attribute during user provisioning.

    User Stores: The user store that a map applies to. If a user logs into a user store that is not in the map’s user store list, that map is not used to read or write attributes for that user.

  3. Use the following guidelines to configure the map:

  4. Click Finish > OK.

  5. Update Identity Server.

Mapping Personal Profile Single-Value Data Items to LDAP Attributes

The data items displayed are single-value Liberty Personal Profile attributes that you can map to the single-valued LDAP attributes that you have defined for your directory.

One-to-One attribute map

Mapping Personal Profile Multiple-Value Data Items to LDAP Attributes

Use this page to map multiple-value attributes from the Liberty Personal Profile to the multiple-value LDAP attributes defined for your directory. For example, map the Liberty attribute Alternate Every Day Name (AltCN) to the LDAP attribute you have defined for this purpose in your directory.

One-to-One attribute map

Mapping Employee Profile Single-Value Data Items to LDAP Attributes

Map the Liberty Employee Profile single-value attributes to the LDAP attributes you have defined in your directory for entries such as ID, Date of Hire, Job Start Date, Department, and so on.

Mapping Employee Profile Multiple-Value Data Items to LDAP Attributes

Map Liberty Employee Profile multiple-value attributes to LDAP attributes defined in your directory.

Mapping Custom Profile Single-Value Data Items to LDAP Attributes

Map custom Liberty profile single-value attributes to LDAP attributes you have defined in your directory. These attributes are customizable strings associated with the Custom Profile.

One-to-One attribute map

Customizable String (1 - 10): The Custom Profile allows custom single-value and multiple-value attributes to be defined without using the Data Model Extension XML to extend a service’s schema. To use a customizable attribute, navigate to the Custom Attribute Names tab on the Custom Profile Details page (see Customizing Attribute Names). Use the page to customize the name of any of the predefined single-value or multiple-value customizable attributes in the Custom Profile. After you customize a name, you can use that attribute in the same way you use any other profile attribute.

Mapping Custom Profile Multiple-Value Data Items to LDAP Attributes

Customizable Multi-Valued Strings (1 - 5): Similar to customizable strings for single-value attributes, except these attributes can have multiple values. Use this list of fields to map directory attributes that can have multiple values to multiple-value strings from the Custom Profile.

Configuring Employee Type Attribute Maps

You can map the LDAP attribute name and values to the Liberty profile values for Employee Type. This is an Employee Profile attribute. Examples of Liberty values appended to this attribute include Contractor Part Time, Contractor Full Time, Full Time Regular, and so on.

  1. Click Devices > Identity Servers > Edit > Liberty > LDAP Attribute Mapping > New > Employee Type.

  2. Specify the following details:

    Name: The name you want to give the map.

    Description: A description of the map.

    Access Rights: If you set this to Read/Write, you can specify rights for individual data items.

    For user provisioning to succeed, you must select Read/Write for any maps that use an attribute during user provisioning.

    User Stores: The user store that a map applies to. If a user logs into a user store that is not in the map’s user store list, that map is not used to read or write attributes for that user.

  3. In LDAP Attribute Name, type the LDAP attribute name that you want to map to the Liberty Employee Type attribute.

  4. In LDAP Attribute Value, type the predefined LDAP attribute values that you want to map to the Liberty Employee Type values.

    These are the values that you want to store in the LDAP attribute for each given Liberty attribute value. The LDAP attribute map then maps the actual Liberty URI value, back and forth, to this supplied value.

  5. Click Finish > OK.

  6. Update Identity Server.

Configuring Employee Status Attribute Maps

You can map the LDAP attribute name and values to the Liberty profile values for Employee Status. This is an Employee Profile attribute. Examples of the values appended to this Liberty attribute include Active, Trial, Retired, Terminated, and so on.

  1. Click Devices > Identity Servers > Edit > Liberty > LDAP Attribute Mapping > New > Employee Status.

  2. Specify the following details:

    Name: The name you want to give the map.

    Description: A description of the map.

    Access Rights: If you set this to Read/Write, you can specify rights for individual data items.

    For user provisioning to succeed, you must select Read/Write for any maps that use an attribute during user provisioning.

    User Stores: The user store that a map applies to. If a user logs into a user store that is not in the map’s user store list, that map is not used to read or write attributes for that user.

  3. In LDAP Attribute Name, type the LDAP attribute name that you want to map to Liberty Employee Status.

  4. In LDAP Attribute Value, type the predefined LDAP attribute values that you want to map to the Liberty Employee Status values.

    These are the values that you want to store in the LDAP attribute for each given Liberty attribute value. The LDAP attribute map then maps the actual Liberty URI value, back and forth, to this supplied value.

  5. Click Finish > OK.

  6. Update Identity Server.

Configuring Postal Address Attribute Maps

You can map the LDAP attribute name and values to the Liberty profile values for Postal Address. The PostalAddress element refers to the local address, including street or block with a house number, and so on. This is a Personal Profile attribute.

  1. Click Devices > Identity Servers > Edit > Liberty > LDAP Attribute Mapping > New > Postal Address.

  2. Specify the following details:

    Name: The name you want to give the map.

    Description: A description of the map.

    Access Rights: If you set this to Read/Write, you can specify rights for individual data items.

    For user provisioning to succeed, you must select Read/Write for any maps that use an attribute during user provisioning.

    User Stores: The user store that a map applies to. If a user logs into a user store that is not in the map’s user store list, that map is not used to read or write attributes for that user.

  3. In Mode, select Multiple LDAP Attributes or Single Delimited LDAP Attributes.

    Multiple LDAP Attributes: Allows you to map multiple LDAP attributes to multiple Liberty Postal Address elements. When you select this option, the following Liberty Postal Address elements are displayed under the Postal Address to LDAP Attributes group. Type the LDAP attributes that you want to map to the Liberty elements.

    • Postal Address

    • Postal Code

    • City

    • State

    • Country

    Single Delimited LDAP Attributes: Allows you to specify one LDAP attribute that is used to hold multiple elements of a Liberty Postal Address in a single delimited value. When you select this option, the page displays the following fields:

    • Delimited LDAP Attribute Name: The delimited LDAP attribute name you have defined for the LDAP postal address that you want to map to the Liberty Postal Address attribute.

    • Delimiter: The character to use to delimit single-value entries. A $ sign is the default delimiter.

  4. (Single Delimited LDAP Attributes mode) Under One-Based Field Position in Delimited LDAP Attribute, specify the order in which the information is contained in the string. For example, select 1 for the value that comes first in the string, 2 for the value that follows the first delimiter.

  5. (Multiple LDAP Attributes mode) Under Postal Address Template Data, specify the following details:

    Nickname: (Required) A Liberty element name used to identify the Postal Address object.

    Contact Method Type: Select the contact method type, such as Domicile > Work, and Emergency.

  6. Click Finish > OK.

  7. Update Identity Server.

Configuring Contact Method Attribute Maps

You can map the LDAP attribute you have defined for contact methods to the Liberty attribute Contact Method (MsgContact).

  1. Click Devices > Identity Servers > Edit > Liberty > LDAP Attribute Mapping > New > Contact Method.

  2. Specify the following details:

    Name: The name you want to give the map.

    Description: A description of the map.

    Access Rights: If you set this to Read/Write, you can specify rights for individual data items.

    For user provisioning to succeed, you must select Read/Write for any maps that use an attribute during user provisioning.

    User Stores: The user store that a map applies to. If a user logs into a user store that is not in the map’s user store list, that map is not used to read or write attributes for that user.

  3. Under Contact Method to LDAP Attributes, specify the following details to map to the Liberty Contact Method attribute:

    Provider LDAP Attribute: Maps to the Liberty attribute MsgProvider, which is the service provider or domain that provides the messaging service.

    Account LDAP Attribute: Maps to the Liberty attribute MsgAccount, which is the account or address information within the messaging provider.

    SubAccount LDAP Attribute: Maps to the Liberty MsgSubaccount, which is the subaccount within a messaging account, such as the voice mail box associated with a phone number.

  4. Under Contact Method Template Data, specify the following details:

    Nickname: Maps to the Liberty attribute Nick, which is an informal name for the contact.

    Type: Maps to the Liberty attribute MsgType (such as Mobile, Personal, or Work).

    Method: Maps to the Liberty MsgMethod (such as Voice, Fax, or E-mail).

    Technology: Maps to the Liberty attribute MsgTechnology (such as Pager, VOIP, and so on).

  5. Click Finish > OK.

  6. Update Identity Server.

Configuring Gender Attribute Maps

You can map the LDAP attribute name and values to the Liberty profile values for the Gender attribute. You can use gender to differentiate between people with the same name, especially in countries where national ID numbers cannot be collected. This is a Personal Profile attribute.

  1. Click Devices > Identity Servers > Edit > Liberty > LDAP Attribute Mapping > New > Gender.

  2. Specify the following details:

    Name: The name you want to give the map.

    Description: A description of the map.

    Access Rights: If you set this to Read/Write, you can specify rights for individual data items.

    For user provisioning to succeed, you must select Read/Write for any maps that use an attribute during user provisioning.

    User Stores: The user store that a map applies to. If a user logs into a user store that is not in the map’s user store list, that map is not used to read or write attributes for that user.

  3. In LDAP Attribute Name, type the LDAP attribute name that you want to map to the Liberty element Gender.

  4. In LDAP Attribute Value, type the predefined LDAP attribute values that you want to map to the Gender values.

    These are the values that you want to store in the LDAP attribute for each given Liberty attribute value. The LDAP attribute map then maps the actual Liberty URI value, back and forth, to this supplied value.

  5. Click Finish > OK.

  6. Update Identity Server.

Configuring Marital Status Attribute Maps

You can map the LDAP marital status attribute to the Liberty attribute. The Liberty Marital Status (MaritalStatus) element includes appended values, such as single, married, and divorced. For example, urn:liberty:id-sis-pp:maritalstatus:single. This is a Personal Profile attribute.

  1. Click Devices > Identity Servers > Edit > Liberty > LDAP Attribute Mapping > New > Marital Status.

  2. Specify the following details:

    Name: The name of the map.

    Description: A description of the map.

    Access Rights: If you set this to Read/Write, you can specify rights for individual data items.

    For user provisioning to succeed, you must select Read/Write from Access Rights for any maps that use an attribute during user provisioning.

    User Stores: The user store that a map applies to. If a user logs into a user store that is not in the map’s user store list, that map is not used to read or write attributes for that user.

  3. In LDAP Attribute Name, type the LDAP attribute name that you want to map to the Liberty element Marital Status (MaritalStatus).

  4. In LDAP Attribute Value, type the predefined LDAP attribute values that you want to map to MaritalStatus values.

    These are the values that you want to store in the LDAP attribute for each given Liberty attribute value. The LDAP attribute map then maps the actual Liberty URI value, back and forth, to this supplied value.

  5. Click Finish > OK.

  6. Update Identity Server.