Mercurial > kallithea
comparison docs/setup.rst @ 775:aaf2fc59a39a beta
fixes #77 and adds extendable base Dn with custom uid specification
author | Marcin Kuzminski <marcin@python-works.com> |
---|---|
date | Fri, 26 Nov 2010 23:49:19 +0100 |
parents | 5f82a00b92b1 |
children | aac24db58ce8 |
comparison
equal
deleted
inserted
replaced
774:c47152c5fe01 | 775:aaf2fc59a39a |
---|---|
111 Base DN = uid=%(user)s,CN=users,DC=host,DC=domain,DC=org | 111 Base DN = uid=%(user)s,CN=users,DC=host,DC=domain,DC=org |
112 | 112 |
113 | 113 |
114 `Account` and `Password` are optional, and used for two-phase ldap | 114 `Account` and `Password` are optional, and used for two-phase ldap |
115 authentication so those are credentials to access Your ldap, if it doesn't | 115 authentication so those are credentials to access Your ldap, if it doesn't |
116 support anonymous search/user lookups. | 116 support anonymous search/user lookups. |
117 | |
118 Base DN must have %(user)s template inside, it's a placer where Your uid used | |
119 to login would go, it allows admins to specify not standard schema for uid | |
120 variable | |
117 | 121 |
118 If all data are entered correctly, and `python-ldap` is properly installed | 122 If all data are entered correctly, and `python-ldap` is properly installed |
119 Users should be granted to access RhodeCode wit ldap accounts. When | 123 Users should be granted to access RhodeCode wit ldap accounts. When |
120 logging at the first time an special ldap account is created inside RhodeCode, | 124 logging at the first time an special ldap account is created inside RhodeCode, |
121 so You can control over permissions even on ldap users. If such user exists | 125 so You can control over permissions even on ldap users. If such user exists |