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

Allow default parameters to web flow in okta.yaml #210

Open
Liz4v opened this issue Jun 13, 2024 · 3 comments
Open

Allow default parameters to web flow in okta.yaml #210

Liz4v opened this issue Jun 13, 2024 · 3 comments
Labels
triaged triaged into Okta's Jira backlog

Comments

@Liz4v
Copy link

Liz4v commented Jun 13, 2024

As far as I can tell from the documentation, the only way to let my team see the list of idps is to force them to fill up org-domain and oidc-client. Sure that's scriptable, but I would prefer to give my team a config file instead, so that the command:

okta-aws-cli web

Would be able to just bring up a list of id providers after authentication.

@Liz4v
Copy link
Author

Liz4v commented Jun 19, 2024

Presumably can be solved by pull request #200

@monde
Copy link
Collaborator

monde commented Jul 8, 2024

@EliseAv is this something different than configure by profile name?

https://github.com/okta/okta-aws-cli?tab=readme-ov-file#configuration-by-profile-name

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

Liz4v commented Jul 10, 2024

Yes. The central problem is that these two behave differently and they should behave exactly the same:

okta-aws-cli web
okta-aws-cli web -p default

@monde monde removed the waiting-response Waiting on collaborator with follow up information label Jul 10, 2024
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
Projects
None yet
Development

No branches or pull requests

2 participants