Generic LDAP format
The table below describes how mail addresses, groups, and user information must be formatted in generic LDAP input.
| Fields | Syntax | Type | Other | |
|---|---|---|---|---|
| Mail fields | ||||
| Primary Mail | %mail% | Directory string Example: jsmith@acme.com | Text |
Mandatory Globally unique |
| Mail aliases/ proxy addresses | %rfc822 mailbox% |
Directory string Example: |
Text |
Optional Globally unique |
| Groups fields | ||||
| Name | %CN% |
Directory string Example: Name, CN, sAMAccountName, Display Name |
Text |
Mandatory Unique in account |
| GUID | %object GUID% |
Hex string Example: 746B8515-C8FF-C940- 9D905F053CB22D25 |
Hex 16 bytes |
Mandatory Unique in account |
| Group Parents | %member Of% |
DN Example: CN=AllStaff,OU=London, DC=acme,DC=com |
Text |
Optional Unique in account |
| Group Members |
%member % |
DN Example: CN=Sales,OU=London,DC =acme,DC=com |
Text |
Optional Unique in account |
| Users fields | ||||
| Name | %CN% |
Directory string Can be constructed dynamically to become the NTLM ID for the user object. A typical NTLM ID is domain\username, for example acme\JSmith. |
Text |
Optional Unique in account |
| Primary Mail | %mail% |
Directory string Must be a valid SMTP email address. |
Text |
Mandatory Globally unique |
| Mail aliases/ proxy addresses | %rfc822m ailbox% |
Directory string Must be a valid SMTP email address. |
Text |
Optional Globally unique |
| Primary Group | %primary GroupId% | Integer Not used | Text | Not used |
| Other Groups | %member Of% |
DN Example: CN=AllStaff,OU=London, DC=acme,DC=com |
Text |
Optional Unique in account |
| GUID | %object GUID% |
Hex string Example: 746B8515-C8FF-C940- 9D905F053CB22D25 |
Hex 16 bytes |
Mandatory Unique in account |