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

Gitea asks for local user password even when connected through OpenID #3521

Open
2 of 7 tasks
arrfab opened this issue Feb 16, 2018 · 11 comments
Open
2 of 7 tasks

Gitea asks for local user password even when connected through OpenID #3521

arrfab opened this issue Feb 16, 2018 · 11 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality

Comments

@arrfab
Copy link

arrfab commented Feb 16, 2018

  • Gitea version (or commit ref): 1.3.2
  • Git version:
  • Operating system: CentOS 7
  • 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

When registered and connected through OpenID, a user even with admin rights has to confirm some operations with his "local" password.
Problem is that $user doesn't know his local password, as he was authenticated/validated/registered through OpenID
There is no even possibility for the user to change his "local" password, as it asks for the actual one (that $user doesn't know, as auto-registered through openid)
It seems the only solution would be for $user to ask a reset of his "local" gitea password , but that defeats completely the SSO goal
...

@rakshith-ravi
Copy link
Contributor

@arrfab I'm using gitea in my server and am planning to switch to OpenID. Is this still happening?

@stale
Copy link

stale bot commented Jan 25, 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 Jan 25, 2019
@lunny
Copy link
Member

lunny commented Jan 25, 2019

I think this is designed. External user have to binding to a local user.

@arrfab
Copy link
Author

arrfab commented Jan 25, 2019

@lunny except that such user doesn't know his "local password" and so can't even change it (as he was automatically registered through OpenID - see bug description)

@stale stale bot removed the issue/stale label Jan 25, 2019
@strk
Copy link
Member

strk commented Jan 27, 2019 via email

@stale
Copy link

stale bot commented Mar 28, 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 Mar 28, 2019
@lunny lunny added type/enhancement An improvement of existing functionality and removed issue/stale labels Mar 29, 2019
@lunny
Copy link
Member

lunny commented Mar 29, 2019

A random password could be set when an external user login and user could change it when he need.

@strk
Copy link
Member

strk commented Apr 4, 2019

A random password could be set when an external user login and user could change it when he need.

This is what my initial implementation of the OpenID-2.0 authentication did. Was it changed recently ?

@strk
Copy link
Member

strk commented Apr 4, 2019

This is the issue I was talking about: #1036
The discussion should happen there

@stale
Copy link

stale bot commented Jun 3, 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 Jun 3, 2019
@MartinX3
Copy link

MartinX3 commented Jun 3, 2019

Please don't close this important issue.

@stale stale bot removed the issue/stale label Jun 3, 2019
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Jun 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality
Projects
None yet
Development

No branches or pull requests

5 participants