docs: add JWT validation guide#731
Open
AtharvaKathe18 wants to merge 1 commit into
Open
Conversation
Signed-off-by: AtharvaKathe18 <atharvakathe567@gmail.com>
3d85f31 to
615f4c5
Compare
Author
|
Hi, just following up on this PR. I’d appreciate any feedback when you have time. Happy to make updates if needed. |
Contributor
|
@AtharvaKathe18 We recently had some JWT additions in other PRs. Can you review what's in there and see if there is anything your PR has that isn't there yet? |
This file contains hidden or 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
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.
Description
This PR adds a JWT validation guide to the security documentation.
Motivation:
While JWT support exists in the API reference, there is no practical guide showing how to configure and use it in a gateway setup.
What changed:
Closes #730
Change Type
/kind documentation
Changelog
Additional Notes
This guide focuses on JWT validation (authentication) and intentionally avoids authorization logic to keep scope aligned with existing documentation patterns.