github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

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

New Issue
Closed
opened 2025-11-02 04:40:27 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 04:40:27 -06:00
Owner
Copy Link

Originally created by @LittleColin on GitHub (Nov 22, 2018).

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.

Originally created by @LittleColin on GitHub (Nov 22, 2018). 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.
GiteaMirror added the issue/staletype/bug labels 2025-11-02 04:40:27 -06:00
GiteaMirror commented 2025-11-02 04:40:29 -06:00
Author
Owner
Copy Link

@tvvignesh commented on GitHub (Dec 19, 2018):

@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 commented on GitHub (Dec 19, 2018): @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?
GiteaMirror commented 2025-11-02 04:40:29 -06:00
Author
Owner
Copy Link

@tvvignesh commented on GitHub (Dec 21, 2018):

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.

@tvvignesh commented on GitHub (Dec 21, 2018): 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.
GiteaMirror commented 2025-11-02 04:40:29 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (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[bot] commented on GitHub (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.
GiteaMirror commented 2025-11-02 04:40:29 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 5, 2019):

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

@stale[bot] commented on GitHub (Mar 5, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/stale type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2559
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?