Skip to content
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

Open
rb1193 opened this issue Sep 22, 2021 · 4 comments
Open

Invalid Client Token ID #21

rb1193 opened this issue Sep 22, 2021 · 4 comments

Comments

@rb1193
Copy link

rb1193 commented Sep 22, 2021

Hi,

Just installed 7777 and getting the following when running 7777 -verbose after specifying an AWS profile and authenticating via SSO:

Using the AWS region ap-southeast-2.
Validating the 7777 license.
Generating unique RSA keys for the SSH tunnel.
Checking if the port 7777 is available.
Port 7777 selected.
Listing databases.
    InvalidClientTokenId: The security token included in the request is invalid.
    Code: InvalidClientTokenId

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

@deleugpn
Copy link
Collaborator

deleugpn commented Sep 22, 2021

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 AWS_PROFILE=your_profile 7777 in case that's relevant.

@rb1193
Copy link
Author

rb1193 commented Sep 22, 2021

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

@deleugpn
Copy link
Collaborator

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.

@rb1193
Copy link
Author

rb1193 commented Sep 22, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants