This repository was archived by the owner on Jan 18, 2025. It is now read-only.
Avoid using expired tokens from credential storage.#173
Merged
craigcitro merged 2 commits intogoogleapis:masterfrom May 12, 2015
Merged
Avoid using expired tokens from credential storage.#173craigcitro merged 2 commits intogoogleapis:masterfrom
craigcitro merged 2 commits intogoogleapis:masterfrom
Conversation
This covers the case where credential storage contains an expired (but different) token, as well as the case where the token read from storage is almost expired and results in a 401 when resending the original request.
Contributor
|
if you say the magic "Closes #158" this will do the needful when i merge. |
Contributor
Author
|
Closes #158 |
Contributor
Author
|
Will look into the failures tomorrow. |
craigcitro
added a commit
that referenced
this pull request
May 12, 2015
Avoid using expired tokens from credential storage.
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
This covers the case where credential storage contains an expired (but different) token, as well as the case where the token read from storage is almost expired and results in a 401 when resending the original request.