fixed #2240 secondary ext-jwt processing would fail... #2242
Conversation
This file contains 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
...if ext-jwt primary wasn't enabled. - fixes extra JWT processing on authentication endpoints (that would never pass) - updates error message for missing NamedIndexStore implementations - fixes ext-jwt store error stating that a named index is not present
plorenz
approved these changes
Jul 16, 2024
- verify up to a max number of jwts (hard coded at 2) - verify by batching and output logging values on failure
|
Added bulk processing for primary plus secondary JWT processing (if configured) |
dovholuknf
approved these changes
Jul 18, 2024
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.
...if ext-jwt primary wasn't enabled.