feat(provider): add OAuth 2.0 client credentials grant type support #279
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 6749 client credentials flow for machine-to-machine authentication: - Add new ClientCredentialsProvider with customizable verify function - Support for custom scopes and token properties - Update issuer to handle client credentials flow in /token endpoint - Add grant_types_supported to .well-known/openid-configuration - Include token_type: "Bearer" in all token responses per OAuth 2.0 spec - Add comprehensive tests for client credentials authentication - Add test to ensure that the endpoint discovery is correct - Add example implementation with service database pattern - Update documentation generation to include new provider The client credentials flow allows services to authenticate directly using client_id and client_secret without user interaction, ideal for API-to-API communication and backend services.
|
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.
Implements RFC 6749 client credentials flow for machine-to-machine authentication:
The client credentials flow allows services to authenticate directly using client_id and client_secret without user interaction, ideal for API-to-API communication and backend services.