Changes for page Use cases of configuration to authenticate users with LDAP
Last modified by Thomas Mortagne on 2019/07/22 14:23
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -6,7 +6,7 @@ 6 6 7 7 1.1 Active Directory 8 8 9 -Here are values of the properties you need to set if your LDAP server implementation is Mi scrosoft Active Directory:9 +Here are values of the properties you need to set if your LDAP server implementation is Microsoft Active Directory: 10 10 - *ldap_server*: name/IP of AD server machine 11 11 - *ldap_port*: port ~~(e.g. 389)~~ 12 12 - *ldap_base_DN*: name of root DN ~~(e.g. dc=ad,dc=company,dc=com)~~ ... ... @@ -44,7 +44,7 @@ 44 44 45 45 1.1 Open Directory Server (OpenDS) 46 46 47 -Here are values of the properties you need to set if your would *authori se only member of a group to login in*.47 +Here are values of the properties you need to set if your would *authorize only member of a group to login in*. 48 48 In this case, the group is cn=xwiki,ou=roles,dc=domain,dc=tld 49 49 50 50 {code} ... ... @@ -62,7 +62,7 @@ 62 62 xwiki.authentication.ldap.user_group=cn=xwiki,ou=roles,dc=domain,dc=tld 63 63 {code} 64 64 65 -*bind_DN* and *bind_pass* are both empty. The connection to the LDAP server will be anonymous. With OpenDS, an anonymous connection can read some needed attributs like userPassword, home, ... 65 +*bind_DN* and *bind_pass* are both empty. The connection to the LDAP server will be anonymous. With OpenDS, an anonymous connection can read some needed attributes like userPassword, home, ... 66 66 67 67 1.1 Generic 68 68 ... ... @@ -97,7 +97,7 @@ 97 97 98 98 1.1.1 My users are not located on the same server 99 99 100 -e.g. if you use several subdomains and the users are defined sep erately in each subdomain. This will likely be the case when you have a configuration like this:100 +e.g. if you use several subdomains and the users are defined separately in each subdomain. This will likely be the case when you have a configuration like this: 101 101 102 102 {code} 103 103 sub1.somedomain.com