Validate JWT supported algorithms against supported set if not provided in config #161
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
This PR changes the handling of
jwt_supported_algs
to be consistent with the behavior prior to PR #155. This means thatjwt_supported_algs
will remain optional and default to the set of algorithms defined in jwt/algs.go#L12-L21 for JWT based authentication.A default of
RS256
is still used for OIDC based authentication.Testing
I've tested that JWT auth works without needing to always provide the correct signing algorithm via
jwt_supported_algs
for both JWKS and static key configurations.