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

Leading zero in account ID not working #96

Closed
monwolf opened this issue Nov 2, 2021 · 0 comments · Fixed by #97
Closed

Leading zero in account ID not working #96

monwolf opened this issue Nov 2, 2021 · 0 comments · Fixed by #97
Labels
bug Something isn't working
Milestone

Comments

@monwolf
Copy link
Contributor

monwolf commented Nov 2, 2021

I have multiple accounts in our ORG and most of them are working fine with this app but we have 2 that starts with a 0, I'm having problems with both when I try to get credentials:

C:\Users\xxx>aws-sso-beta exec --role AdministratorAccess  -A "032043643619" --level=debug
level=warning msg="Using insecure json file for SecureStore: C:\\Users\\xxx/aws-sso/store.json" func=main.main file="/mnt/d/Proyectos/aws-sso-cli/cmd/main.go:131"
level=debug msg="Fetching STS token from AWS SSO" func=main.GetRoleCredentials file="/mnt/d/Proyectos/aws-sso-cli/cmd/main.go:220"
level=fatal msg="Unable to get role credentials for AdministratorAccess" func=main.GetRoleCredentials file="/mnt/d/Proyectos/aws-sso-cli/cmd/main.go:226" error=": No access\n\tstatus code: 403, request id: "
@monwolf monwolf changed the title Leading zero accounts ID not working Leading zero in accounts ID not working Nov 2, 2021
@monwolf monwolf changed the title Leading zero in accounts ID not working Leading zero in account ID not working Nov 2, 2021
@synfinatic synfinatic added the bug Something isn't working label Nov 2, 2021
@synfinatic synfinatic added this to the 1.2.1 milestone Nov 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants