allow to pass in alternative signing algoritm to RFC7523 JWT client assertions #390
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 kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
Referencing #389:
I'd like to have control over the signing algoritms used for the JWT client asserstion authentication variants. The current API doesn't allow to override the default RS256, even thought the lower-level signing helper functions are parameterized.
When setting up an PrivateKeyJWT() instance to register as client auth method, I'd like to pass in the signing algoritm I'd like to use.