Commit 390f0b76b51d966b2ac429c28d07fbec5497a4c0

Authored by Jacob Vosmaer
1 parent dba98240

Explain allow_username_or_email_login LDAP setting

Showing 1 changed file with 5 additions and 0 deletions   Show diff stats
config/gitlab.yml.example
@@ -127,6 +127,11 @@ production: &base @@ -127,6 +127,11 @@ production: &base
127 method: 'ssl' # "ssl" or "plain" 127 method: 'ssl' # "ssl" or "plain"
128 bind_dn: '_the_full_dn_of_the_user_you_will_bind_with' 128 bind_dn: '_the_full_dn_of_the_user_you_will_bind_with'
129 password: '_the_password_of_the_bind_user' 129 password: '_the_password_of_the_bind_user'
  130 + # If allow_username_or_email_login is enabled, GitLab will ignore everything
  131 + # after the first '@' in LDAP the username submitted by the user on login.
  132 + # Example:
  133 + # - the user enters 'jane.doe@example.com' and 'p@ssw0rd' as LDAP credentials;
  134 + # - GitLab queries the LDAP server with 'jane.doe' and 'p@ssw0rd'.
130 allow_username_or_email_login: true 135 allow_username_or_email_login: true
131 136
132 ## OmniAuth settings 137 ## OmniAuth settings