Closed hulto closed 1 week ago
Please confirm your ROOT_URL
is the right one.
http://git.galaxygridlabs.com:3000/ui/vault/identity/oidc/provider/default/authorize?client_id=wWOeykAzVxxRDJpQEGRVnuYtef0Au6HZ&redirect_uri=http%3A%2F%2Fgit.galaxygridlabs.com%3A3000%2Fuser%2Foauth2%2Fvault2%2Fcallback&response_type=code&scope=openid&state=b0ad9b74-e2a9-4d4f-ae54-6e9e6baff1ec
It is "vault"'s problem. According to OIDC spec, the URLs in the "well-known openid configuration" should be a FULL URL.
https://openid.net/specs/openid-connect-discovery-1_0.html
But your vault only responds a relative path without scheme or host.
Ahh thanks @wxiaoguang you're totally right.
Description
I'm trying to configure gitea with my vault server as an authentication source using Oauth2. I followed the prompts under: Identity & Access > Authentication Sources > Add Authentication Source
When I login to gitea with my custom Oauth2 source. Sign in > Sign in > Sign in with vault2
gitea redirects me to: http:///
Instead of the expected:
https:///
Resulting in a 404.
Gitea Version
1.22.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
Auth source configuration
openid-configuration JSON
Signing in with OpenID vault2
Unexpected 404 error
Git Version
No response
Operating System
No response
How are you running Gitea?
Docker image
docker.io/gitea/gitea:1.22.3@sha256:76f516a1a8c27e8f8e9773639bf337c0176547a2d42a80843e3f2536787341c6
Using GCP COS.Setup with pulumi golang.
Database
SQLite