Differences

This shows you the differences between two versions of the page.

--- 72:ldap_url_attribute [2018/07/16 12:40] – [URL Attribute] bkkr
+++ 72:ldap_url_attribute [2018/07/16 12:41] – [URL Attribute] bkkr
@@ Line 5: / Line 5: @@
 The url attribute is used to set the LDAP URL of the server to be queried. The attribute is structured in the following way:
-''<font inherit/Courier New,Courier,monospace;;inherit;;inherit><ldap>://<ldap-server>:<port>/<ldap_directory_to_be_queried>//</font>''
+<font inherit/Courier New,Courier,monospace;;inherit;;inherit><ldap>://<ldap-server>:<port>/<ldap_directory_to_be_queried></font>
-''<font inherit/Courier New,Courier,monospace;;inherit;;inherit>//]//</font>//'' The following table describes how to fill this schema with concrete values:
+The following table describes how to fill this schema with concrete values:
- ^Schema Value ^Description|
-|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 "ldaps".|
-|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.|
-|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: '' [[false|url=”ldap://ldapsrv.methodpark.de:389/OU=User,DC=pkit,DC=methodpark,DC=de]]“ ''\\
-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. //''