Fill basic info for users auto-created using a reverse proxy

[Kegeruneku]

As quoted from #165 :

Greetings @unknwon !

I would also be interested in having a way to have a way to fill basic info about the user auto-created by ENABLE_REVERSE_PROXY_AUTO_REGISTRATION.

As said by previous commenters, it could either be passed using http headers, or if available using a configured LDAP provider (this is what others application usually do when applicable)

The use case is simple: I would love to at least have the correct mail for the user so he/she does not have to redefine profile info after initial login. (it is needed for mails to be sent in case of updates and having to redefine it is tedious especially when the info is actually already available somewhere)

The user first name / last name would be a bonus (if possible, but the mail is more important)

I'll be around if you need precisions :)

[unknwon]

Thanks your feedback!

[Kegeruneku]

Also, it might be a good idea to be able to set a default identification provider for newly created users, in case the user that was auto created comes from an identification provider known to Gogs (a LDAP server, maybe). This way, you would be able to provision automatically all user details

I think the best approach would be, in case a new user unknown to Gogs just authenticated using headers, to search for this user in the configured authentication providers, and if the user is not found fallback to what Gogs already does: create a local user with a randomly generated password and mail.

The bonus point would be a setting to tell gogs if a user can not be found in the authentication backend, to refuse the login, but it's not really necessary in a first iteration

[unknwon]

Thanks for your comments!

Just want to point out that the basic rule of this feature is: everything come from header is valid, no check process should be performed by Gogs. This is my understanding...

[dortamur]

We've started to use Gogs for our team's code archive, and this feature would be great! While we could use an LDAP source for the extra user identity data, getting the core fields from headers provided by the Auth proxy would be fine for us (and simpler).

[sid3windr]

I'd greatly prefer to keep everything inside GOGS; it's nice that accounts are now autocreated but they are indeed missing the name and e-mail fields currently. It would be nice to have a "default provider" for that (i.e. a configured LDAP auth backend), and have it pull the user's data from that backend upon creation.

I think we'll make do for now with an outside script that fills in missing data for e-mails ending in @localhost.

[elvarb]

having a setting to define the default created passwords would help

ENABLE_REVERSE_PROXY_AUTO_REGISTRATION_EMAIL = X-Forwarded-Email

or

ENABLE_REVERSE_PROXY_AUTO_REGISTRATION_EMAILNAME = X-Forwarded-User
ENABLE_REVERSE_PROXY_AUTO_REGISTRATION_EMAILDOMAIN = "company.com"