Validate the access token before pass to the API request where we can avoid 401 failure #1
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
To use manual trigger for silent refresh token
…st, potentially resulting in a silent redirect In certain situations, the access token may expire before an API request, potentially resulting in a silent redirect. The challenge arises when ongoing requests lack of ability to update the access token dynamically, leading to failures when interacting with the API. To address this, I've made adjustments to proactively check for token expiration. If expired, a manual silent redirect is triggered to obtain a new token, ensuring subsequent API calls use the updated access token
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In certain situations, the access token may expire before an API request, potentially resulting in a silent redirect.
The challenge arises when ongoing requests lack of ability to update the access token dynamically, leading to failures when interacting with the API. To address this, I've made adjustments to proactively check for token expiration. If expired, a manual silent redirect is triggered to obtain a new token, ensuring subsequent API calls use the updated access token.