-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Implement well known OpenID Configuration #8775
Comments
I think that's the part of OpenID provider standard but gitea doesn't implement. |
Yes. Interestingly, there is a reference to this endpoint here: gitea/options/locale/locale_en-US.ini Line 1772 in 232340f
Sadly I don't think it is relevant at all 🙂 |
I have started implementing it |
@lafriks Glad to see someone is working on it! Any news when we can except this feature to be merged? Thanks a lot! |
I'm planning to finish it for 1.12 |
How would this work when Gitea is running in a subpath (ie, example.com/gitea/)? I'm thinking we could probably put in docs that it isn't supported for for subpath installations (because .well-known has to be served from root path) |
@techknowlogick that is not true, it is supported to have it also in subpath |
Hi there. I've been researching about OpenID Connect because I'm really interested in centralize auth credentials in gitea for our dev team. I still don't fully undertand OIDC but correct me if I'm wrong. Would it be possible to implement my own As far as I understand, that file is some sort of mapper of the available oauth endpoints and grant types, right? |
any news update? |
AFAIC this works already? |
No, still missing |
any news update? |
|
Looks like well-known and userinfo are merged. this can be closed then? |
Description
The PR #5378 initially implemented the OAuth2 provider. I love the idea to have gitea as my SSO provider :-)
However, it seems like the
.well-known/...
endpoints are missing. This is also stated in the PR, "will be implemented in another PR".I'm trying to get ArgoCD to work (see this), and it seems like it tries to connect to
https://<server>/ .well-known/openid-configuration
, which does not exist and returns a 401.I guess this goes into the same direction as #8534.
Would be cool if gitea had support for that as well!
Edit: More info on the endpoint can be found here
The text was updated successfully, but these errors were encountered: