tom-smith-okta / okta-awscli-java Goto Github PK

I like to use this docker image more like a script, having it update my AWS profile outside of the container:

docker run --rm \
  -v ~/.okta/config.properties:/root/.okta/config.properties \
  -v ~/.aws/:/root/.aws/ \
  -it tomsmithokta/okta-awscli-java:1.0.3 \
  "/bin/bash" "-c" "withokta aws $PROFILE_NAME sts get-caller-identity"

The nice thing is that this updates the AWS profile on my host and lets me run aws commands there without having to inject the okta profile argument into those commands. However, this doesn't keep the association of the target account with the target profile name (i.e. /root/.okta/profiles), nor does it keep the session cookie.

One simple approach to resolving this would be to mount not just the config.properties file, but the whole ~/.okta/ directory. Unfortunately, because the bash_functions and okta-aws-cli.jar both live in that directory, they get hidden if the whole directory is mounted.

Could those files live elsewhere in the container? In the mean time, I'm stuck with having to create them before hand and mount them individually.

The latest version of the assume role tool opens a web browser. This just doesn't work anymore. Should we consider this project closed, or any plans to make this work again?

Thanks.