Skip to content

allow reverse proxy auth to provide user full name #20775

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
willnorris opened this issue Aug 12, 2022 · 0 comments · Fixed by #20776
Closed

allow reverse proxy auth to provide user full name #20775

willnorris opened this issue Aug 12, 2022 · 0 comments · Fixed by #20776
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Milestone

Comments

@willnorris
Copy link
Contributor

Feature Description

Today, gitea supports external authentication using the reverse proxy auth. It currently supports getting the username and email from the reverse proxy. It would be great if it also supported getting the user's full name from the reverse proxy if it's available.

For example, grafana's external auth supports getting full name (and a handful of other attributes that make sense for them). And similarly, Tailscale's nginx-auth can provide the user's full name. I'm an engineer at Tailscale, and ran into this when setting up gitea on my home network.

I have a working patch and will submit that shortly.

Screenshots

No response

@willnorris willnorris added type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels Aug 12, 2022
@lunny lunny added this to the 1.18.0 milestone Aug 16, 2022
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants