-
Notifications
You must be signed in to change notification settings - Fork 346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fails to read cached SSO token when AWS profile config includes a sso_session
attribute
#771
Comments
From this issue it seems like if a new release is cut from the current source on main, the issue may be resolved. The released version's |
Hi @schrobot, version 0.8.0 has been released; however, I was unable to reproduce the issue on the previous v0.7.1 version. Can you confirm the Amazon ECR credential helper version you encountered the issue? i.e. output from Also as a sanity check, can you confirm you set the |
I'm still experiencing this issue. (v0.9.0) |
@endzyme Thank You. |
Yes, I can confirm it's the same An example that you could try to reproduce is allowing SSO users to have a maximum session duration of 12 hours, but a token duration of two hours. I'm actually away from work for a few weeks and cannot test but that's what I recall for now. I can help reproduce it when I'm back in mid march. |
see aws/aws-sdk-go#5184
Reproduction Steps
~/.aws/config
enabled for SSO, that has a session-nameaws sso login --profile <that profile>
session_name
attribute, and login againThe text was updated successfully, but these errors were encountered: