Skip to content

Option to lock full name when using external auth sources #31958

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
thezzisu opened this issue Sep 3, 2024 · 1 comment · Fixed by #31959
Closed

Option to lock full name when using external auth sources #31958

thezzisu opened this issue Sep 3, 2024 · 1 comment · Fixed by #31959
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@thezzisu
Copy link
Contributor

thezzisu commented Sep 3, 2024

Feature Description

In certain scenarios (such as within schools), users registered through external authentication need to maintain their real names.

Since names may contain Unicode characters (like a Chinese name), a good practice is to set DEFAULT_SHOW_FULL_NAME=true and set the user's full name to their real name. In this situation, it's necessary to ensure that external users cannot modify their own full name.

An option like EXTERNAL_USER_LOCK_FULL_NAME would be great to fit this need.

Screenshots

image

@thezzisu thezzisu added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Sep 3, 2024
@thezzisu
Copy link
Contributor Author

thezzisu commented Sep 3, 2024

I am currently writing a PR for this.
Also, a working example is implemented in a fork, but I think it would be better to have this functionality built-in.

@lunny lunny closed this as completed in 66923e0 Oct 5, 2024
@go-gitea go-gitea locked as resolved and limited conversation to collaborators Jan 3, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
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.

1 participant