forkjo/routers/admin
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
..
admin.go add admin op: delete missing repos 2015-11-18 15:37:48 -05:00
auths.go LDAP: Optional user name attribute specification 2015-12-02 00:20:14 +01:00
notice.go fix #1930 2015-11-12 12:32:40 -05:00
orgs.go New admin organization UI 2015-09-25 19:54:52 +02:00
repos.go #1693 minor fix 2015-09-25 19:07:21 -04:00
users.go #1511 Allow local import only for admin users 2015-11-03 18:40:52 -05:00