Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
72:ldap_url_attribute [2018/07/16 12:44] – [URL Attribute] bkkr | 72:ldap_url_attribute [2018/07/16 12:45] – [URL Attribute] bkkr | ||
---|---|---|---|
Line 12: | Line 12: | ||
|ldap|The LDAP URL starts with a protocol prefix which is normally set to “ldap“. If you want to encrypt the synchronization process via SSL, use " | |ldap|The LDAP URL starts with a protocol prefix which is normally set to “ldap“. If you want to encrypt the synchronization process via SSL, use " | ||
|ldap-server|The fully qualified domain name of the LDAP server| | |ldap-server|The fully qualified domain name of the LDAP server| | ||
- | |port |The TCP port the LDAP server is listening on. The standard TCP port for unencrypted LDAP communication is 389, whereas 636 is used for secure communication.| | + | |port|The TCP port the LDAP server is listening on. The standard TCP port for unencrypted LDAP communication is 389, whereas 636 is used for secure communication.| |
|ldap_directory_to_be_queried|The distinguished name of the directory to be queried, including the server’s base dn.| | |ldap_directory_to_be_queried|The distinguished name of the directory to be queried, including the server’s base dn.| | ||
+ | |||
+ | A sample url attribute setting is given as follows: | ||
+ | |||
+ | ''< | ||
+ | |||
+ | As mentioned above, configuring LDAP is a very customer specific task. Therefore the value of the url attribute can differ quite strongly from the example given above. | ||
\\ | \\ | ||