Refresh SSO AccessToken if first attempt errors out #281
Conversation
This file contains 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
synfinatic
force-pushed
the
expired-session-token
branch
2 times, most recently
from
982b829 to
486b16c
Compare
For some reason our SSO AccessTokens are being marked as invalid by AWS SSO API and so the sso.GetAccounts() and sso.GetRoles() calls should try force reauthenticating once to AWS SSO in order to get a new AccessToken for these calls. Fixes: #279
synfinatic
force-pushed
the
expired-session-token
branch
from
486b16c to
8ff2a3a
Compare
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.
For some reason our SSO AccessTokens are being marked as invalid
by AWS SSO API and so the sso.GetAccounts() and sso.GetRoles()
calls should try force reauthenticating once to AWS SSO in order to get a
new AccessToken for these calls.
Refs: #279