gitea/modules/auth
Adam Strzelecki 573305f3d3 LDAP: Optional user name attribute specification
Consider following LDAP search query example:

    (&(objectClass=Person)(|(uid=%s)(mail=%s)))

Right now on first login attempt Gogs will use the text supplied on login form
as the newly created user name. In example query above the text matches against
both e-mail or user name. So if user puts the e-mail then the new Gogs user
name will be e-mail which may be undesired.

Using optional user name attribute setting we can explicitly say we want Gogs
user name to be certain LDAP attribute eg. `uid`, so even user will use e-mail
to login 1st time, the new account will receive correct user name.
2015-12-02 00:20:14 +01:00
..
apiv1 fix import path, fix #1782 2015-10-15 21:28:12 -04:00
ldap LDAP: Optional user name attribute specification 2015-12-02 00:20:14 +01:00
pam use pam and update TRANSLATORS 2015-07-14 19:47:20 +08:00
admin.go #1511 Allow local import only for admin users 2015-11-03 18:40:52 -05:00
auth_form.go LDAP: Optional user name attribute specification 2015-12-02 00:20:14 +01:00
auth.go work on #470 and fix miror JS issue when choose targets on compare and pull 2015-10-29 21:09:48 -04:00
org.go UI: long organization name in create repository owner list 2015-11-18 17:42:20 -05:00
repo_form.go wiki: finish edit 2015-11-27 01:50:38 -05:00
user_form.go #470 fix max length of email 2015-10-29 21:12:41 -04:00