endpoints for auth discovery / metadata#30
Draft
JoshuaGabriel wants to merge 2 commits into
Draft
Conversation
replace the gateway's post-only custom handler map with HTTP route metadata so direct handlers can register methods needed. Signed-off-by: Joshua Blanch <joshua.blanch@clyso.com>
expose public auth metadata so clients can discover the oauth token/revoke endpoints + locate jwt key based on RFC 8615 Signed-off-by: Joshua Blanch <joshua.blanch@clyso.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
makes consumers of API able to discover the oauth token/revoke endpoints + locate jwt key
endpoints
/.well-known/ceph-api
/.well-known/ceph-api/jwks.json
based on this https://datatracker.ietf.org/doc/html/rfc8615
based ontop of the persistence pr #28