github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-22 14:34:54 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

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

New Issue
Closed
opened 2025-11-02 10:42:32 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 10:42:32 -06:00
Owner
Copy Link

Originally created by @thezzisu on GitHub (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

Originally created by @thezzisu on GitHub (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](https://github.com/user-attachments/assets/01b06801-24f2-4803-900b-741cf874e161)
GiteaMirror added the type/proposal label 2025-11-02 10:42:32 -06:00
GiteaMirror commented 2025-11-02 10:42:33 -06:00
Author
Owner
Copy Link

@thezzisu commented on GitHub (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.

@thezzisu commented on GitHub (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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#13443
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?