Bad OAuth2 OpenID Connect management with invalid URL #5830

New Issue

GiteaMirror · 2025-11-02T06:37:13-06:00

GiteaMirror commented

2025-11-02 06:37:13 -06:00

Originally created by @fmarcia on GitHub (Aug 5, 2020).

Gitea version (or commit ref): 1.12.3
Git version: 2.28.0
Operating system: linux amd64
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: https://gist.github.com/fmarcia/d140d16c5f02318e87497451ececb027

Description

I prepared a new OAuth2 OpenID Connect source with a fake auto-discovery URL and I've got an error 500 after validation but the new source has been saved. I tried to change the fake URL with a more specific one, but still fake. This time, I have got an error specifying the URL is not accessible and the new URL has not been saved.

From there, I could not restard Gitea service (see log where it's specified the URL is not useable) until I removed the faulty source in db.

Originally created by @fmarcia on GitHub (Aug 5, 2020). - Gitea version (or commit ref): 1.12.3 - Git version: 2.28.0 - Operating system: linux amd64 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: https://gist.github.com/fmarcia/d140d16c5f02318e87497451ececb027 ## Description I prepared a new OAuth2 OpenID Connect source with a fake auto-discovery URL and I've got an error 500 after validation but the new source has been saved. I tried to change the fake URL with a more specific one, but still fake. This time, I have got an error specifying the URL is not accessible and the new URL has not been saved. From there, I could not restard Gitea service (see log where it's specified the URL is not useable) until I removed the faulty source in db.

GiteaMirror added the issue/stale label 2025-11-02 06:37:13 -06:00

GiteaMirror commented

2025-11-02 06:37:14 -06:00

@techknowlogick commented on GitHub (Aug 6, 2020):

FWIW oauth management is also available via CLI (https://docs.gitea.io/en-us/command-line/#admin) so if this happens again, then you don't need to fiddle with DB.

@techknowlogick commented on GitHub (Aug 6, 2020): FWIW oauth management is also available via CLI (https://docs.gitea.io/en-us/command-line/#admin) so if this happens again, then you don't need to fiddle with DB.

GiteaMirror commented

2025-11-02 06:37:14 -06:00

@fmarcia commented on GitHub (Aug 6, 2020):

@techknowlogick thanks to remind me that

@fmarcia commented on GitHub (Aug 6, 2020): @techknowlogick thanks to remind me that

GiteaMirror commented

2025-11-02 06:37:15 -06:00

@stale[bot] commented on GitHub (Oct 12, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Oct 12, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#5830