feat: OAuth 2.0 Dynamic Client Registration Protocol (RFC 7591) #4383
Conversation
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
Implements RFC 7591 OAuth 2.0 Dynamic Client Registration Protocol, allowing clients to register dynamically at runtime via HTTP API. Features: - `POST /register` endpoint for client registration - Request/response types compliant with RFC 7591 - Support for both confidential and public clients (PKCE) - Optional authentication via initial access token - Default values per RFC spec (`grant_types`, `response_types`, etc.) - Validation of grant types and response types - Discovery endpoint includes `registration_endpoint` field Signed-off-by: ByteBaker <[email protected]>
ByteBaker
force-pushed
the
feat/dynamic-client-registration
branch
from
ef33e87 to
fcedca4
Compare
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.
Overview
Implements RFC 7591 OAuth 2.0 Dynamic Client Registration Protocol, allowing clients to register dynamically at runtime via HTTP API.
What this PR does / why we need it
POST /registerendpoint for client registrationgrant_types,response_types, etc.)registration_endpointfield