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
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
admin.go
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_sqlite.go
models_tidb.go
models.go
org.go
publickey.go
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
update.go
user.go	finish wiki	2015-11-30 20:45:55 -05:00
webhook_slack.go
webhook.go
wiki.go	fix API	2015-12-01 16:33:45 -05:00