-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Add OpenID Connect Discovery Endpoint #27
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
Comments
This is also required to support #30 as it calls this endpoint. |
@anoopgarlapati Thank you for the offer! Let's find another task for you to contribute as this one is lower on the priority. We need to focus on implementing core OAuth 2.0 before we get into OpenID Connect 1.0. I'm in the process of putting together a roadmap that will prioritize the features to be developed. I will log an issue that provides a link to the roadmap along with the first set of epics and associated issues. Please take a look at the next set of issues (coming this week) and let me know which ones interest you and we can assign to you. Sounds good? |
@jgrandja Sounds good and I understand. Looking forward to contributing. Thanks! |
An authorization server should support the
/.well-known/openid-configuration
endpoint as specified by https://openid.net/specs/openid-connect-discovery-1_0.html.This enables automatic client configuration (as already implemented in spring security 5) and we can also integrate JWKS endpoint as of gh-2.
The Nimbus SDK may be used for generating the endpoint response.
The text was updated successfully, but these errors were encountered: