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

[[RFE] : creating users when authenticated through defined authentication source (like oauth2) #3520

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

Comments

@arrfab
Copy link

arrfab commented Feb 16, 2018

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

Not a bug but request for enhancement : Actually, gitea permits users logged it through openid to have the corresponding user automatically created in gitea :
ENABLE_OPENID_SIGNIN = true
ENABLE_OPENID_SIGNUP = true

But it doens't work if one decides to create a authentication source like oauth2 (so tested with OpenID Connect on my side) : once authenticated, and redirected to gitea, it asks to either :

  • login with existing (local) user (doesn't exist yet)
  • create a new user account

Of course I'd like to only allow people authenticated through oauth2 to sign in and so be registered automatically (so DISABLE_REGISTRATION = true)

As discussed in #gitea on freenode, creating a RFE ticket here so that people can discuss it and/or track a potential status change

...

@stale
Copy link

stale bot commented Jan 23, 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 23, 2019
@lunny lunny added issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented and removed issue/stale labels Feb 7, 2019
@schmitch
Copy link

schmitch commented Apr 5, 2019

is there actually some progress on this?

@jolheiser
Copy link
Member

@schmitch Looks like #5123 is the current PR

@6543
Copy link
Member

6543 commented Apr 14, 2021

closed by #5123

@6543 6543 closed this as completed Apr 14, 2021
@6543 6543 added this to the 1.15.0 milestone Apr 14, 2021
@go-gitea go-gitea locked and limited conversation to collaborators Jun 4, 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/enhancement An improvement of existing functionality
Projects
None yet
Development

No branches or pull requests

5 participants