feat: Add documentation for proactive token refresh and session-only auth #2273
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.
This PR enhances the examples to include patterns for proactive token refresh and session-only authentication. It also clarifies important considerations for refresh token rotation.
Fixes: #2149
📋 Changes
These changes provide developers with more advanced and robust patterns for handling tokens and sessions. The proactive refresh example helps prevent API call failures due to expired tokens in latency-sensitive applications.
EXAMPLES.md
: Added a note ongetSession
usage, a warning about refresh token rotation, and a new example for proactive token refresh. Corrected the import path forwithPageAuthRequired
.README.md
: Fixed minor list formatting.🎯 Testing
Manual:
EXAMPLES.md
.getSession
, refresh token rotation, and proactive token refresh for clarity and accuracy.