docs: list all JWKS sources in the security guide - #173
Merged
Merged
Conversation
commit: |
kallebysantos
approved these changes
Sep 18, 2026
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
2 participants
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.
The JWT verification section of
docs/security.mdsaid the key set comes only fromSUPABASE_JWKSand that verification never touches the network. Both statements predateSUPABASE_JWKS_URLand the well-known endpoint derived fromSUPABASE_PUBLIC_URLorSUPABASE_URLin #167. The three affected lines now list the source order, describe how a URL source is fetched and cached under jose's cooldown and max-age rules with the https-or-loopback transport rule, and state that user mode is unavailable only when no source resolves at all. The full resolution order stays indocs/environment-variables.md, which the section now points to.