chore: add pattern restriction on continuation_token
#215
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
justincoh
changed the title
continuation_token
justincoh
changed the title
continuation_tokencontinuation_token
justincoh
commented
Dec 20, 2024
jpadilla
approved these changes
Dec 30, 2024
This was referenced Dec 30, 2024
aaguiarz
pushed a commit
that referenced
this pull request
Jan 13, 2026
* add pattern restriction on continuation_tokens * update continuation_token regex to be specific to url base64
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
OpenFGA already rejects tokens which contain base64-invalid characters in its handlers. This PR is an added layer of protection to ensure that an invalid token won't make it to the handling functions at all.
References
Review Checklist
main