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

New error thrown for ".okta/okta.yaml" not found #226

Closed
estokes-vs opened this issue Aug 1, 2024 · 3 comments · Fixed by #232
Closed

New error thrown for ".okta/okta.yaml" not found #226

estokes-vs opened this issue Aug 1, 2024 · 3 comments · Fixed by #232
Assignees

Comments

@estokes-vs
Copy link

I've upgraded today from okta-aws-cli 2.1.2 -> 2.3.0 and there appears to be a new error that is being thrown that likely could be resolved by the program itself.

The command we use to authenticate is below:

okta-aws-cli --org-domain <DOMAIN> --oidc-client-id <CLIENT_ID> --aws-acct-fed-app-id <AWS_ACCT_FED_APP_ID> --format aws-credentials --open-browser --write-aws-credentials --session-duration <DURATION> --cache-access-token --expiry-aws-variables

And the new error is:

WARNING: issue with okta.yaml file. Run `okta-aws-cli debug` command for additional diagnosis.
Error: open /Users/<USERNAME>/.okta/okta.yaml: no such file or directory

I verified that this pops up each time we run the command but never is resolved automatically by the system, but it feels like it could be. Can the okta-aws-cli just create this folder and file if it doesn't exist, or emit an error if it's unable to create the items due to local permissions?

@rmadoori754
Copy link

I have same issue

@monde
Copy link
Collaborator

monde commented Aug 27, 2024

I will clean this up ...

@monde
Copy link
Collaborator

monde commented Aug 28, 2024

#232

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

Successfully merging a pull request may close this issue.

3 participants