diff options
| author | cos <cos> | 2015-06-03 16:54:08 +0200 |
|---|---|---|
| committer | cos <cos> | 2015-06-03 16:54:08 +0200 |
| commit | 17be0e24fd346e341da8c20edc24c3df3d5bfdc0 (patch) | |
| tree | 60f43ce9b0dda1f25206cb5251c95174595b3ade | |
| parent | 459c7f9328ce2f3aaaede8197e50103080592efc (diff) | |
| download | taiga-contrib-ldap-auth-topic/taiga/auth_ldap_suffix.zip | |
Update README.md to mention LDAP_SEARCH_SUFFIX.topic/taiga/auth_ldap_suffix
| -rw-r--r-- | README.md | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -32,6 +32,7 @@ LDAP configuration: LDAP_SEARCH_BASE = 'OU=DevTeam,DC=example,DC=net' # LDAP property used for searching, ie. login username needs to match value in sAMAccountName property in LDAP LDAP_SEARCH_PROPERTY = 'sAMAccountName' + LDAP_SEARCH_SUFFIX = None # '@example.com' # Names of LDAP properties on user account to get email and full name LDAP_EMAIL_PROPERTY = 'mail' @@ -42,6 +43,8 @@ The logic of the code is such that a dedicated domain service account user perfo If the search is successful, then the code uses this value and the typed-in password to attempt a bind to LDAP using these credentials. If the bind is successful, then we can say that the user is authorised to log in to Taiga. +Optionally LDAP_SEARCH_SUFFIX can be set to allow for the search to match only the beginning of a field containing e.g. an email address. + If the LDAP_BIND_DN configuration setting is not specified or is blank, then an anonymous bind is attempted to search for the login user's LDAP account entry. |