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.

Sign up for GitHub

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

Jump to bottom

Cache credentials for future use #7

Closed

justinm opened this issue Nov 13, 2017 · 1 comment

Labels

Milestone

justinm commented Nov 13, 2017

To supplement #6, it'd be nice to also have a way to more easily authenticate more terminals than just one.

New flags: --use-cache

User Authentication Workflow

User authenticates via okta-awscli
okta-awscli saves credentials to ~/.kube/okta-awscli.credentials each time
User runs okta-awscli --use-cache on each terminal
- If credentials are cached
  - okta-awscli re-exports the cached credentials
  - okta-awscli exits with status code 0
- If credentials are not cached
  - okta-awscli re-exports the cached credentials
  - okta-awscli exits with status code -1

Automated Workflow

User authenticates via okta-awscli
okta-awscli saves credentials to ~/.kube/okta-awscli.credentials each time
User prepends okta-awscli --use-cache to each script
- If credentials are cached
  - okta-awscli re-exports the cached credentials
  - okta-awscli exits with status code 0
- If credentials are not cached
  - okta-awscli re-exports the cached credentials
  - okta-awscli exits with status code -1
Example: okta-awscli --use-cache

The text was updated successfully, but these errors were encountered:

jmhale added the enhancement label

jmhale added this to the v0.2.0 milestone

justinm mentioned this issue

Cache credentials #23

Merged

jmhale mentioned this issue

Merge develop into v0.2.0 #25

Merged

Member

jmhale commented Feb 11, 2018

Fixed in #25

jmhale closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment