Adjust documentation about JWT reuse #24243
Merged
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
eviljeff
approved these changes
Dec 12, 2025
| The JWT will have a short expiration time and is only valid for a single | ||
| request so you can't cache or reuse it. | ||
| Prior to making API requests, you need to generate a `JWT`_. | ||
| The JWT will have a short expiration time but can be re-used until they expire. |
Member
There was a problem hiding this comment.
should we go further, and encourage their re-use?
Member
Author
There was a problem hiding this comment.
I'd prefer to move slow and observe for now - don't want developers to start storing tokens on disk for instance...
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.
Fixes: mozilla/addons#15966