573305f3d3
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. |
||
---|---|---|
.. | ||
cron | ||
migrations | ||
access.go | ||
action.go | ||
admin.go | ||
error.go | ||
git_diff.go | ||
issue.go | ||
login.go | ||
models_sqlite.go | ||
models_tidb.go | ||
models.go | ||
org.go | ||
publickey.go | ||
pull.go | ||
release.go | ||
repo.go | ||
token.go | ||
update.go | ||
user.go | ||
webhook_slack.go | ||
webhook.go | ||
wiki.go |