# User Service Data to LDAP Attributes Mapping

## Purpose

Use this form to map corporate directory (LDAP
Lightweight Directory Access Protocol is a software protocol for enabling anyone to locate organizations, individuals, and other resources such as files and devices in a network. LDAP is a "lightweight" (smaller amount of code) version of DAP (Directory Access Protocol), which is part of X.500, a standard for directory services in a network.) user data to the MiVoice Business user data.

MiVoice Business, via the Integrated Directory Services (IDS)
IDS synchronizes user and service data between a corporate directory server and MiVoice Business IDS (or MiCollab if in the same network cluster) using the Lightweight Directory Access Protocol (LDAP). Once the data is synchronized, it is distributed from the MiVoice Business IDS to the various member elements in the SBS network or cluster. application, uses the map to convert LDAP queries that it receives from the directory server into internal User Service Data recognized by MiVoice Business. The mapping enables you to reuse information in the corporate LDAP directory to provision MiVoice Business users .

If a user service data field has a mapped LDAP attribute that is not set from the directory server or is not returned from an LDAP query, then "default handling" is used to program the field on MiVoice Business. The following default handling options are available:

- None - Default handling is not applied. If the field is blank, it remains blank.

- Template - A User and Service Template provides the missing value. If the user role is known, its template is used. Otherwise, the default template is used.

- System Defined - Default handling is applied by the system. For details, see the field descriptions below.

In the current release, the form provides mapping for the Microsoft Active Directory (AD) service. Support for other directory services will be added in a later release.

Use this form when performing the following tasks:

- Configuring IDS on MiVoice Business

- Implementing MiVoice Business IDS on an SDS Network

- Migrating from OPS Manager IDS to MiVoice Business IDS

For more information:

- What Data is Synchronized

NOTE: MiVoice Business also provides a built-in LDAP server and an interface to servers running OpenLDAP, an open source implementation of LDAP. Both are used by 69xx IP Phones to populate its native Phone Book application with user data. For more information, see LDAP Client Configuration.

## Conditions

- The form is programmed with a default set of LDAP attributes for Microsoft Active Directory (AD). Update the values only if your server is using non-default LDAP attributes.

- LDAP attributes must be programmed for the following User Service Data fields: First Name, Last Name, and User ID. All other fields can have blank LDAP Attributes, which enables them to be updated from a User and Service Template or the directory server, or to remain blank. To clear all non-essential fields, click the Clear button.

- When updating an LDAP attribute in the map, bear in mind that it should:

- belong to the user object class

- be programmable from a GUI tool such as the Users and Computers console

- use the same syntax as the user service data (for example, "User ID" and "ObjectGUID" both contain GUID)

- be single-valued (recommended but not essential)

- be included in the Global Catalog PAS if you intend to synchronize with the GC for all domains in your network; for more information, see IDS General Guidelines and Limitations

- LDAP attributes must be unique.

## Field Descriptions

User Service Data Field Data from the MiVoice Business User and Services Configuration form to map to LDAP | Description | Default Value
LDAP Attribute A default set of LDAP attributes for Microsoft Active Directory (AD). Update the values only if your server is using non-default LDAP attributes | Default Handling Defines how to program fields on MiVoice Business when a user service data field has a mapped LDAP attribute that is not set from the directory server or is not returned from an LDAP query.
First Name | Enter the LDAP attribute for the user first name. Default handling is always "System Defined." If both this field and the Last Name are blank, the update fails and is posted to the IDS Data Management form with an "application error" status. NOTE: An LDAP attribute must be programmed for this field. | givenName | System Defined
Last Name | Enter the LDAP attribute for the user last name. Default handling is always "System Defined." If both this field and the First Name are blank, the update fails and is posted to the IDS Data Management form with an "application error" status. NOTE: An LDAP attribute must be programmed for this field. | sn | System Defined
User ID | Enter the LDAP attribute for the user object identifier that serves as unique key for the record. Default handling is always "System Defined." If this field is blank, the system will cause the update to fail and add a message to the error log. NOTES Unlike other user service data, the User ID does not appear on the ESM interface. It serves as a key only. An LDAP attribute must be programmed for this field. | ObjectGUID | System Defined
Login ID | The Login ID attribute provides compatibility with applications, including MiCollab and MiVoice Business, that rely on the availability of Login ID data. It is not required by MiVoice Business for phone service. If the Login ID data is given, a default password must be set via a User and Service Template. Default handling is always "None." |  | None
Department | Enter the LDAP attribute for the department and select a default handling option: Template - If the field is blank, a User and Service Template provides the missing value. None - If the field is blank, it remains blank. | department | Template
Location | Enter the LDAP attribute for the location and select a default handling option: Template - If the field is blank, a User and Service Template provides the missing value. None - If the field is blank, it remains blank. | physicalDeliveryOfficeName | Template
Language | Enter the LDAP attribute for the language and select a default handling option: Template - If the field is blank, a User and Service Template provides the missing value. None - If the field is blank, it remains blank. | preferredLanguage | Template
Role | Enter the LDAP attribute for the user role. Default handling is always "None." | employeeType | None
Directory Number | Enter the LDAP attribute for the directory number. Default handling for this attribute is always "None." | telephoneNumber | None
Home Element | Enter the LDAP attribute for the home element. Default handling is always "None." | ipPhone | None
Secondary Element | Enter the LDAP attribute for the secondary element and select a default handling option: Template - If the field is blank, a User and Service Template provides the missing value. None - If the field is blank, it remains blank. | otherIpPhone | None
Email | Enter the LDAP attribute for the email address. Default handling is always "None." | mail | None