[SDK-3858] Support JWT Client Authentication #507
Merged
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.
Changes
Adds the ability to authenticate using JWT Client Authentication instead of a client secret.
New classes:
ClientAssertionSigner
- interface that defines the contract to create signed client authentication JWTsRSAClientAssertionSigner
- implementation that supports RS256 and RS384 signingNew methods:
AuthAPI.Builder#withClientAssertionSigning(ClientAssertionSigner signer)
- configure the builder to use client assertion signingUsage:
A static method has also been added to
AuthAPI
for convenience:References
https://openid.net/specs/openid-connect-core-1_0-15.html#ClientAuthentication
Testing
In addition to unit tests, tested using a client configured for client authentication and specified
withClientAssertionSigner
using an RSA signer from a public key in PEM format.