-
Notifications
You must be signed in to change notification settings - Fork 3
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
Invalid Client Token ID #21
Comments
Are you trying to assume role with MFA? That unfortunately is not supported as per #15 (comment) Could you perhaps try without the MFA just to confirm if that's the problem? PS.: as a happy coincidence I was actually working on MFA support today. I'm not sure about SSO, though as that's something only supported by AWS CLI v2, correct? We developed 7777 before the release of cli v2. You can also run |
Thanks for the quick response. Still no luck with MFA disabled. I am running AWS CLI v2 as you guessed, I suspect that or the SSO login will be the issue |
AWS CLI isn't really an issue because we use nodejs sdk, not the cli itself. The problem will be SSO as it's something we never faced before. |
That makes sense, thank you. I will try creating a new IAM user and authenticating that way. Feel free to close, unless you're thinking of adding SSO support any time soon. |
Hi,
Just installed 7777 and getting the following when running
7777 -verbose
after specifying an AWS profile and authenticating via SSO:I am able to run all other AWS CLI commands against the account. I feel like I'm probably missing something obvious - am I missing an IAM permission perhaps? MFA is enabled on the account in case that's relevant.
Thanks
The text was updated successfully, but these errors were encountered: