Mapping User Details from LDAP Server to Adeptia Server

It is very likely that the Adeptia Server and LDAP Server uses different parameters to store their user accounts information. Therefore, while configuring LDAP, you will be required to map the user details from your LDAP server to Adeptia Server. To configure mapping between the two servers, Adeptia Suite provides ldapConfiguration.xml file, which is stored in ServerKernel/etc folder of your Adeptia Suite. After successful retrieval of LDAP user object (based on specified base DN and base filter) and authentication, it's attributes are queried to map it to Adeptia user attributes so that similar user can be created inside Adeptia. If retrieval of specified attribute from LDAP user object fails, it is populated with NA. So, all of them are optional except "uniqueIdentifier" which specifies the attribute through which user is uniquely identified in LDAP Server and we need this attribute value for creating user in Adeptia.
The configurable ldapConfiguration.xml file has each field for user in Adeptia Suite as tag which contains the following two attributes:

Mapped-to: This attribute contains the name of attribute which is to be mapped with user detail in Adeptia Server.
Default-value: This attribute contains the default value, such as NA, if the attribute defined in above section does not have any value or does not exist in Adeptia Server.

The following screen shot displays the tags and attributes in the ldapConfiguration.xml file (see Figure 6 ):

Figure 6: Tags and Attributes in ldapConfiguration.xml file

Detail of each field of LdapConfiguration.xml File:

Field Name	Field Description	Sample or Possible Values (for "mapped-to" element in configuration XML)	Default Value (in case value From mapped attribute can't be fetched – specified by "default-value" element in configuration XML)	Mandatory
uniqueIdentifier	It specifies the user attribute that defines its uniqueness in LDAP Server.	uid (for OpenLDAP) sAMAccountName (for Active Directory)	-	Yes
firstName	It specifies the user attribute that defines its first name.	givenName	N.A.	No
lastName	It specifies the user attribute that defines its last name.	sn	N.A.	No
description	It specifies the user attribute that defines any description about the user.		LDAP user	No
address1	It specifies the user attribute that defines its address.	streetAddress	N.A.	No
address2	It specifies the user attribute that defines its address.		N.A.	No
city	It specifies the user attribute that defines city where user resides.	l	N.A.	No
state	It specifies the user attribute that defines state where user resides.	st	N.A.	No
zip	It specifies the user attribute that defines zip of state where user resides.	-	N.A.	No
country	It specifies the user Attribute that defines country where user resides.	co	N.A.	No
fax	It specifies the user Attribute that defines its fax #.	facsimileTelephoneNumber	N.A.	No
phone	It specifies the user Attribute that defines its phone #.	telephoneNumber	N.A.	No
mobile	It specifies the user attribute that defines its mobile #.	mobile	N.A.	No
email	It specifies the user attribute that defines its email id.	mail	email@company.com	No
title	It specifies the user Attribute that defines its title.	title	N.A.	No
comment	It specifies the user attribute that defines any comment for it.	-	N.A.	No
orgName	It specifies the user attribute that defines name of organization where user works.	company	N.A.	No
orgUrl	It specifies the user attribute that defines URL of organization where user works.	-	N.A.	No