jwt_authn: supports jwt payload without "iss" field #12744
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.
To fix #12377
If jwt payload doesn't use "iss" to specify issuer, not to extract issuer, and not verify it with the config. In most cases, the config from the required provider is used to extract jwt token, not need to verify its issuer.
In
allow_missing
orallow_fail_or_missing
cases, all providers are used, "iss" is needed to extract issuer to lookup specific provider.Risk Level: Low
Testing: add unit-test
Docs Changes: Yes