Skip to content
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

Bug: Users authenticated via proxy-auth can change username #2407

Closed
MTecknology opened this issue Aug 27, 2017 · 5 comments · Fixed by #15304
Closed

Bug: Users authenticated via proxy-auth can change username #2407

MTecknology opened this issue Aug 27, 2017 · 5 comments · Fixed by #15304
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug

Comments

@MTecknology
Copy link
Contributor

MTecknology commented Aug 27, 2017

In the current version of gitea, it is possible for users authenticated via proxy-auth to edit their username. I'm not able to find a config option to disable this. In cases where proxy authentication is being used, this allows users to change their username and orphan their repositories because a new userid will be immediately created with their correct user.

@bkcsoft
Copy link
Member

bkcsoft commented Aug 27, 2017

I think in the case of proxy auth (or oauth/openid) we should disallow username changes.

@lafriks
Copy link
Member

lafriks commented Aug 28, 2017

Only local users are allowed to change username and I don't think that somehow affects linked openid etc authorization that is handled otherwise and just links to account and are not authorization source

@MTecknology MTecknology changed the title New Feature (/bug): Option to permit changing user names Bug: Users authenticated via proxy-auth can change username Aug 28, 2017
@stale
Copy link

stale bot commented Feb 13, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Feb 13, 2019
@ptman
Copy link
Contributor

ptman commented Feb 13, 2019

Yes, this is a problem

@stale stale bot removed the issue/stale label Feb 13, 2019
@stale
Copy link

stale bot commented Apr 14, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Apr 14, 2019
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Apr 14, 2019
@stale stale bot removed the issue/stale label Apr 14, 2019
zeripath added a commit to zeripath/gitea that referenced this issue Apr 5, 2021
zeripath added a commit to zeripath/gitea that referenced this issue Apr 6, 2021
…annot change username

ReverseProxy users should generate a session on reverse proxy username change.

Also prevent ReverseProxy users from changing their username.

Fix go-gitea#2407

Signed-off-by: Andrew Thornton <[email protected]>
6543 pushed a commit that referenced this issue May 15, 2021
…annot change username (#15304)

* Create a session on ReverseProxy and ensure that ReverseProxy users cannot change username

ReverseProxy users should generate a session on reverse proxy username change.

Also prevent ReverseProxy users from changing their username.

Fix #2407

* add testcase

Signed-off-by: Andrew Thornton <[email protected]>
AbdulrhmnGhanem pushed a commit to kitspace/gitea that referenced this issue Aug 10, 2021
…annot change username (go-gitea#15304)

* Create a session on ReverseProxy and ensure that ReverseProxy users cannot change username

ReverseProxy users should generate a session on reverse proxy username change.

Also prevent ReverseProxy users from changing their username.

Fix go-gitea#2407

* add testcase

Signed-off-by: Andrew Thornton <[email protected]>
@go-gitea go-gitea locked and limited conversation to collaborators Oct 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug
Projects
None yet
5 participants