-
Notifications
You must be signed in to change notification settings - Fork 34
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
support for aws-cli credential_process #119
Comments
I was looking at https://docs.aws.amazon.com/sdkref/latest/guide/feature-process-credentials.html when I originally implemented okta-aws-cli. At the time the okta-aws-cli required user input so implementing process credentials with not possible because I found the AWS CLI completely swallows stdout/stderr. Since then I think it's possible to run okta-aws-cli without human input if the IdP and Role pre-select flags are used in otka-aws-cli . Also, I'm working on a headless feature for okta-aws-cli so this would be a good time to add process-credentials suport. |
Okta internal reference: https://oktainc.atlassian.net/browse/OKTA-642837 |
I've been using this as a workaround for this in
|
Cool work around on v1 @jkiang13 |
I tried the most reset v2 version and I'm running into this error message:
If I follow the answer above to generate process-credentials with awk it works fine. |
Process credential support is the v2 release, but it has a bug if you try to combine it with also writing the credential file that has been fixed. That bug is fixed and will be released later this week. Here's an example of how I run int in my local env:
I should have closed this issue with the v2 release. |
I would like to hook okta-aws-cli as credential_process to the aws cli. reference: https://docs.aws.amazon.com/sdkref/latest/guide/feature-process-credentials.html
this way I can use my aws cli directly without having to run a separate command to get the credentials via okta-aws-cli
This is how saml2aws implements it:
https://github.com/Versent/saml2aws#using-saml2aws-as-credential-process
So what we would need is
The text was updated successfully, but these errors were encountered: