search

oktadev / okta-aws-cli-assume-role

Okta AWS CLI Assume Role Tool
Apache License 2.0
338 stars 177 forks source link

creds and profile not updating after expired creds #290

Open marklaczynski opened 5 years ago

marklaczynski commented 5 years ago

On version 2.0 As per instructions to run okta-aws test sts get-caller-identity

The first pass runs correctly and updates ~/.okta/profile and ~/.aws/credentials files

however, after the credentials expire and you run okta-aws test sts get-caller-identity again, the above file do not update. I assume there are some other state config that isn't being updated, because the only way I've been able to get around this is to delete ~/.okta and reinstall from a clean slate.

marklaczynski commented 5 years ago

So I found out why ~/.aws/credentials file was not being updated. As part of the user-error, I set OKTA_ENV_MODE=true

borislubimov commented 5 years ago

Had the same issue due to the fact that I had AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables set in my system. After I remove them the issue was solved.

UPDATE: Issue reproduced again, the only way which helped to solved it was to downgrade java to 1.8.0_161

ghost commented 5 years ago

I'm running into the same issue

openjdk 13 2019-09-17
OpenJDK Runtime Environment (build 13+33)
OpenJDK 64-Bit Server VM (build 13+33, mixed mode, sharing)

I have a clean method that resets everything

function okta-aws-clean {
  rm -f $HOME/.okta/.current-session
  rm -f $HOME/.okta/profiles
  rm -f $HOME/.okta/cookies.properties
}

~I've confirmed that explicitly setting export OKTA_ENV_MODE=false fixes the issue. It seems that the default in the readme is not true?~ This seems to be a fluke...