Skip to main content
ZenHub houses documentation to support you if you’re using Contensis Classic. Contensis Classic includes our WYSIWYG and templating features. If you’re working with a newer version of Contensis, is your go-to place to find anything Contensis-related when building with content types.
There is a newer version of Contensis. Click to find out more and download the latest version.

AD integration custom mappings

There are two settings that allow you to customise AD synchronisation behaviour. Each setting is specified in the format "parta-partb" separated by a comma.

Part A refers to the AD setting found in Available Active Directory properties listed below and part b is described under the respective headings below.


This mapping is designed to map directly to properties on the Contensis User Object, CMS_API.Security.User. Using an object explorer will show each of the properties available, but we have provided some examples below:

A valid Example would be: ExtensionAttribute1-AddressTown

Active Directory to CMS Mappings
AdditionalInfo Gets or sets any extra information to be associated with the user usually used in the Who's Who
Address1 This Address property usually stores the County for the user.
Address2 This Address property stores the County for the user.
AddressCountry This Address property stores the Country for the user.
AddressCounty This Address property stores the County for the user.
AddressPostcode This Address property stores the Country for the user.
AddressTown This Address property stores the Town for the user.
Biography Gets or sets the biographical information pertinent to the user often used within Who's Who
BlogUrl Gets or sets the url of the user's Blog
CompanyName Gets or sets the name of the company the user is associated with.
DateOfBirth This property is used to store the users Date of Birth
DaylightSavings Gets or sets a value indicating whether [daylight savings].
Department Gets or sets the department.
DirectDialNumber This property returns the DirectDialNumber (DDI) for the user.
Email Email address
FaxNumber Gets or sets the fax number.
FirstName Firstname of the user
JobRole Gets or sets the job role of the user.
JobTitle Gets or sets the user job title.
Lastname Gets or sets the lastname.
Location Gets or sets the location.
MessengerAIM Gets or sets the address of the user's AIM Instant Messaging Account
MessengerGoogleTalk Gets or sets the address of the user's GoogleTalk Instant Messaging Account
MessengerICQ Gets or sets the address of the user's ICQ Instant Messaging Account
MessengerJabber Gets or sets the address of the user's Jabber Instant Messaging Account
MessengerSkype Gets or sets the address of the user's Skype Instant Messaging Account
MessengerWindowsLive Gets or sets the address of the user's Windows Live(MSN) Instant Messaging Account
MessengerYahoo Gets or sets the messenger yahoo.
Mobile Mobile Number for the user.
Nationality Gets or sets the nationality of the user
NickName Nickname used for applications such as chat and discussion forums.
ProfileStatement Gets or sets the profile statement.
RelationshipStatus Gets or sets the relationship status of the user, when used in social networking.
Sex Gets or sets the sex of the user.
Signature Gets or sets the signature, usually used within forums.
Telephone Telephone number for the user.
TimeZoneId Gets or sets the time zone id.
TimeZoneOffset Get/Set timezone offset
Title Title of the User i.e Mr,Mrs etc.
WebsiteAddress This Property returns the Website Address for a user, usually their blog url or similar.


These mapping work in the same way as the CMS mappings, except that you are mapping to custom properties against a user. In effect you could map any AD property to any named property that you make up, and this would then be available through the Custom Properties associated with a user, like seen below.


An example would be extensionAttribute1-My_made_up_property.

Available Active Directory properties

Note: these values are case sensitive!


This list is the list of properties that you can use to map to Contensis custom properties or user properties.

  • FirstName
  • LastName
  • EMailAddr
  • TelNo
  • Title
  • Department
  • Division
  • JobTitle
  • HomePage
  • Description
  • Initials
  • Mobile
  • Office
  • Manager
  • UName
  • IsAccountDisabled
  • IsAccountLocked
  • ExtensionAttribute1
  • ExtensionAttribute2
  • ExtensionAttribute3
  • ExtensionAttribute4
  • ExtensionAttribute5
  • ExtensionAttribute6
  • ExtensionAttribute7
  • ExtensionAttribute8
  • ExtensionAttribute9
  • ExtensionAttribute10
  • ExtensionAttribute11
  • ExtensionAttribute12
  • ExtensionAttribute13
  • ExtensionAttribute14
  • ExtensionAttribute15

Custom mappings to LDAP user attributes

The AD Update also supports updating AD user record properties using the standard LDAP attribute names ( listed here ). These can be included in the DirectoryServices_ADToCMSMappings and DirectoryServices_ADToCustomMappings global settings using the LDAP attribute names instead of the Active Directory properties listed above, e.g.facsimileTelephoneNumber-FaxNumber would map the Contensis user's fax number to the LDAP user attribute facsimileTelephoneNumber.

Due to the large number of different LDAP user attributes, not all have been tested with Contensis, so it may not be possible to use some of them. LDAP attribute names are not supported by AD Synchronisation.

Custom mappings to array-based LDAP user attributes

The AD Update also supports mapping Contensis user properties to array-based LDAP user attributes, e.g. an address with multiple lines. These can be included in the DirectoryServices_ADToCMSMappings and DirectoryServices_ADToCustomMappings global settings by simply including the array-based LDAP user attribute more than once, e.g. streetAddress-Address1, streetAddress-Address2 would map both the Contensis user's Address1 and Address2 fields to the LDAP user attribute streetAddress, adding each value in the order specified.

Note: This functionality is not supported by AD Synchronisation.