We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
[x]
Hello, I am adding an oauth2 OIDC authentication source via the CLI with the following command:
gitea admin auth add-oauth --name keycloak --provider openidConnect --key git-client --secret $SECRET --auto-discover-url https://login.mydomain.net/auth/realms/merlin/.well-known/openid-configuration
The entry shows up correct under the GUI (screenshot below).
Unfortunately, when clicking the login with OIDC button at login, I am given the 500 error:
no provider for keycloak exists
The problem is resolved by clicking "update authentication source" under the GUI without making any changes.
To test, I tried running this command but without resolution:
gitea admin auth update-oauth --id 1 --name keycloak
I would expect that adding the the OIDC source via CLI would not require this extra step through the GUI.
Has anyone else had this issue?
Thank you kindly for any pointers.
The text was updated successfully, but these errors were encountered:
This worked for me after restarting Gitea.
I would like to see configuration options directly in app.ini.
app.ini
Sorry, something went wrong.
fixed via #14116
No branches or pull requests
[x]
):Description
Hello, I am adding an oauth2 OIDC authentication source via the CLI with the following command:
The entry shows up correct under the GUI (screenshot below).
Unfortunately, when clicking the login with OIDC button at login, I am given the 500 error:
The problem is resolved by clicking "update authentication source" under the GUI without making any changes.
To test, I tried running this command but without resolution:
I would expect that adding the the OIDC source via CLI would not require this extra step through the GUI.
Has anyone else had this issue?
Thank you kindly for any pointers.
Screenshots
The text was updated successfully, but these errors were encountered: