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

Using --all-profiles with no access to ListAccountAliases api call #218

Open
azisi opened this issue Jul 8, 2024 · 2 comments
Open

Using --all-profiles with no access to ListAccountAliases api call #218

azisi opened this issue Jul 8, 2024 · 2 comments
Labels
triaged triaged into Okta's Jira backlog waiting-response Waiting on collaborator with follow up information

Comments

@azisi
Copy link

azisi commented Jul 8, 2024

When using --all-profiles to get all available credentials, some roles may not have access to the ListAccountAliases api call. An example is the AWS Managed PowerUserAccess role. This produces a non-intuitive profile name in .aws/credentials.

Furthermore, if you have multiple cases in the same idp the failover default name is identical and credentials get overwritten.

It would be nice to add a section to the config yaml for known aliases in order to render the names correctly.

I can provide a PR if this feature would be considered.

@monde
Copy link
Collaborator

monde commented Jul 8, 2024

Thanks @azisi that would be awesome if you could make time to do a PR for this enhancement!

@monde monde added triaged triaged into Okta's Jira backlog waiting-response Waiting on collaborator with follow up information labels Jul 8, 2024
@mervin-hemaraju-cko
Copy link

Hey @azisi, any update on this one? I am getting the same issue as well!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triaged triaged into Okta's Jira backlog waiting-response Waiting on collaborator with follow up information
Projects
None yet
Development

No branches or pull requests

3 participants