github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Add support for reverse proxy header authentication with email alone #9056

New Issue
Closed
opened 2025-11-02 08:27:27 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 08:27:27 -06:00
Owner
Copy Link

Originally created by @mhlakhani on GitHub (Jun 12, 2022).

Feature Description

Hi!

I saw it's possible to authenticate using a reverse proxy by sending an X-Webauth-User header. Optionally (if enabled in settings), if the X-Webauth-Email header is provided a user is also auto-registered.

For my internal setup at home, my reverse proxy does not have access to gitea usernames, but the sign in system has access to emails. Would it be possible to extend the code to allow authenticating just via the contents of X-Webauth-Email?

I'm happy to try and put up a PR myself if there are no objections to this feature.

Screenshots

No response

Originally created by @mhlakhani on GitHub (Jun 12, 2022). ### Feature Description Hi! I saw it's possible to authenticate using a reverse proxy by sending an `X-Webauth-User` header. Optionally (if enabled in settings), if the `X-Webauth-Email` header is provided a user is also auto-registered. For my internal setup at home, my reverse proxy does not have access to gitea usernames, but the sign in system has access to emails. Would it be possible to extend the code to allow authenticating just via the contents of `X-Webauth-Email`? I'm happy to try and put up a PR myself if there are no objections to this feature. ### Screenshots _No response_
GiteaMirror added the type/proposaltype/feature labels 2025-11-02 08:27:27 -06:00
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/feature 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#9056
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?