chore: jwt examples #642
Merged
chore: jwt examples #642
Conversation
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
Adding a middleware template to validate Legacy Supabase JWT tokens
Contributor
|
Adding examples is always welcome! Good job @kallebysantos ! btw this is just adding an example, right? So to avoid version changes during merging, we should change the |
Member
Author
|
Sure! thank you for explain me that 💚 |
nyannyacha
approved these changes
Nov 12, 2025
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.
What kind of change does this PR introduce?
docs update
What is the new behaviour?
Since jwt verification will be deprecated, users should use
--no-verify-jwtand do verification by their selves.This PR adds some templates for jwt token verification.
Additional context