feat: implement oauth2 client credentials auth profile#48
Merged
Conversation
c70620e to
5b6d5ed
Compare
5b6d5ed to
48ed415
Compare
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
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.
What
Implements oauth2 client credentials auth profile
How
By registering the authorization profile on the Dataplane instance:
And registering the control-plane with such profile, every call made to that control-plane will be done by requesting a new jwt token to the configured tokenUrl with clientId and clientSecret attributes.
NOTE: this is not much more than an example, a more fine tuned implementation with token caching and refresh would be up to the user.
Additional notest
AuthorizationProfileusage easier and less convolutedCloses #42