Skip to content

Support Reverse Proxy Email #2347

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
2 of 7 tasks
MTecknology opened this issue Aug 21, 2017 · 2 comments
Closed
2 of 7 tasks

Support Reverse Proxy Email #2347

MTecknology opened this issue Aug 21, 2017 · 2 comments
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Milestone

Comments

@MTecknology
Copy link
Contributor

  • Gitea version (or commit ref): master
  • Git version: 2.11.0
  • Operating system: Debian
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

The option REVERSE_PROXY_AUTHENTICATION_USER option allows users to be created, which is great, but I noticed the email address tends to look something like this, c8147db3-4a42-a6b3-8642-d7c33fc55365@localhost. I'm not sure where that value comes from, but I'm pretty confident it's relatively useless.

When the proxy is providing authentication information, I imagine the user's email address is readily available to the proxy. In this case, it would be helpful if the option REVERSE_PROXY_AUTHENTICATION_EMAIL could be added so that the value can be correctly filled out during registration.

It'd also be nice if there were an option to automatically update the address if it changes.

@lafriks lafriks added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Aug 21, 2017
@lafriks lafriks added this to the 1.x.x milestone Aug 21, 2017
@lafriks
Copy link
Member

lafriks commented Aug 21, 2017

Other option would be to define email domain and have emails generated in form username@domain

@MTecknology
Copy link
Contributor Author

MTecknology commented Aug 21, 2017

We already have two domains that might be used and potentially more.

zeripath added a commit to zeripath/gitea that referenced this issue Dec 17, 2018
techknowlogick pushed a commit that referenced this issue Dec 18, 2018
@lafriks lafriks modified the milestones: 1.x.x, 1.7.0 Dec 19, 2018
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
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.
Projects
None yet
Development

No branches or pull requests

3 participants