search

Nike-Inc / gimme-aws-creds

A CLI that utilizes Okta IdP via SAML to acquire temporary AWS credentials
Apache License 2.0
925 stars 263 forks source link

LOGIN ERROR but no keychain entry found #377

Closed danielgelmanKH closed 1 year ago

danielgelmanKH commented 1 year ago

One of my users is having trouble logging in. She is getting the following error:

%gimme-aws-creds Stored password is invalid, clearing. Please try again LOGIN ERROR: Authentication failed | Error Code: E0000004

I understand this is to be expected if the password stored in keychain is wrong. However: 1)She was unable to find a keychain entry when searching for gimme-aws-creds 2)The error persisted even after multiple attempts until, the error changed to a lockout message

I looked at the okta logs and the attempts also show an incorrect password, so I don't think this is a connection failure.

I think this may be the same problem this comment (https://github.com/Nike-Inc/gimme-aws-creds/issues/160#issuecomment-1031087069) refers to, but it's unclear since the commenter doesn't follow up at all

Expected Behavior: Either 1)The user is prompted to enter a new password after a 2nd run of the command, or 2)A keychain entry is found when searching for "gimme"

App Version used: 2.4.4 installed via homebrew Environment name and version: terminal Operating System and version: MacOS 11.7

danielgelmanKH commented 1 year ago

I found the solution: run unset OKTA_PASSWORD and the rerun gimme-aws-creds