Skip to content

OpenID Connect authentication source gives 500 error with "SignIn: no provider for foo exists" #5380

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
5 tasks
LittleColin opened this issue Nov 22, 2018 · 4 comments

Comments

@LittleColin
Copy link

I am adding an Authentication Source for OpenID Connect. I've tried several OpenID Connect providers but all of them result in the following error when I click the OpenID Connect logo on the login screen so I suspect it's not even trying to use the configuration.

[...routers/user/auth.go:520 SignInOAuth()] [E] SignIn: no provider for foo exists

(where foo is whatever name I gave the authention name in the free-text field)

  • Gitea version (or commit ref): e08c7e5
  • Git version: n/a
  • Operating system:
  • Database (use [x]):
    • [ X ] PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • [ X ] Not relevant - no admin access to try
  • Log gist:

Description

See above

Screenshots

Just shows 500 error after clicking OpenID Connect logo on login screen.

@lunny lunny added the type/bug label Nov 23, 2018
@tvvignesh
Copy link

@lunny I got the same 500 error when trying Office 365 Sign In via OpenID. Is this fixed?

Also, I was wondering if there is a way to restrict only users from a specific domain to login - is it available in Gitea?

@tvvignesh
Copy link

Got the 500 error fixed by fixing my autodiscovery URL and upgrading to Gitea 1.6.1 but still wondering how to restrict signups to a domain.

@stale
Copy link

stale bot commented Feb 19, 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 19, 2019
@stale
Copy link

stale bot commented Mar 5, 2019

This issue has been automatically closed because of inactivity. You can re-open it if needed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants