nathan-v / aws_okta_keyman

AWS Okta Keyman (Key Manager) - An AWS + Okta CLI for generating and managing local AWS API keys
https://nathanv.com
Other
59 stars 35 forks source link

Command ./aws_okta_keyman.exe get stuck in (INFO) Using account: #172

Closed LeoHeidji closed 7 months ago

LeoHeidji commented 7 months ago

Describe the bug After configure the aws_okta_keyman on Windows and execute the command: ./aws_okta_keyman.exe I only see 2 lines in the command prompt:

13:49:26 (INFO) AWS Okta Keyman \U0001f510 v0.9.0 13:49:26 (INFO) Using account: FET / aaaaik3onbui9H4yzzzz/272

To Reproduce Steps to reproduce the behavior:

  1. After install and configure aws_okta_keyman, execute on Windows through Git Bash the command: ./aws_okta_keyman.exe
  2. ...
  3. ...
  4. ...

Expected behavior Roles will be found, temporary credential should be created

Prompt AL123000@ABC-CCE-CLD-107 MINGW64 ~/AppData/Roaming/Python/Python39/Scripts $ ./aws_okta_keyman.exe 13:49:26 (INFO) AWS Okta Keyman \U0001f510 v0.9.0 13:49:26 (INFO) Using account: FET / aaaaik3onbui9H4yzzzz/272

Host (please complete the following information):

C:\WINDOWS\system32>pip list Package Version


aws-okta-keyman 0.9.0 beautifulsoup4 4.12.2 boto3 1.28.78 botocore 1.31.78 certifi 2023.7.22 charset-normalizer 3.3.2 colorama 0.4.6 colorlog 6.7.0 configparser 6.0.0 idna 3.4 importlib-metadata 6.8.0 jaraco.classes 3.3.0 jmespath 1.0.1 keyring 24.2.0 more-itertools 10.1.0 pip 22.0.4 python-dateutil 2.8.2 pywin32-ctypes 0.2.2 PyYAML 6.0.1 requests 2.31.0 s3transfer 0.7.0 setuptools 58.1.0 six 1.16.0 soupsieve 2.5 urllib3 1.26.18 zipp 3.17.0

LeoHeidji commented 7 months ago

Config: username: AL123000 org: exampleorg accounts:

LeoHeidji commented 7 months ago

Resolved the issue by configuring Okta to authenticate through MFA and using CMD instead Git Bash