forgejo/models
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
..
cron simplify names 2015-09-16 23:08:46 -04:00
migrations add unsupported migration prompt 2015-11-25 09:27:27 -05:00
access.go fix #1997 2015-11-19 11:40:00 -05:00
action.go fix api broken 2015-11-15 17:07:44 -05:00
admin.go New admin notice UI based on user list example 2015-09-25 18:13:38 +02:00
error.go wiki: finish edit 2015-11-27 01:50:38 -05:00
git_diff.go better escape char handle 2015-11-20 01:18:50 -05:00
issue.go fix for #2012 2015-11-21 14:02:37 -05:00
login.go LDAP: Optional user name attribute specification 2015-12-02 00:20:14 +01:00
models.go fix #1902 2015-11-07 00:39:45 -05:00
models_sqlite.go go vet 2014-04-13 03:14:43 -04:00
models_tidb.go add tidb support 2015-09-12 15:31:36 -04:00
org.go New admin organization UI 2015-09-25 19:54:52 +02:00
publickey.go fix #878 2015-11-18 21:21:47 -05:00
pull.go wiki: finish edit 2015-11-27 01:50:38 -05:00
release.go wiki: finish new 2015-11-27 00:24:24 -05:00
repo.go fix #2042 2015-11-30 20:50:40 -05:00
token.go finish all new user settings UI 2015-09-10 11:40:34 -04:00
update.go Show custom avatars in commits 2015-11-13 17:10:25 -05:00
user.go finish wiki 2015-11-30 20:45:55 -05:00
webhook.go fix #878 2015-11-18 21:21:47 -05:00
webhook_slack.go webhook APIs 2015-08-29 11:49:59 +08:00
wiki.go fix API 2015-12-01 16:33:45 -05:00