Skip to content
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.

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

Store client token in endpoint-specific file #2096

Closed

Conversation

mfischer-zd
Copy link
Contributor

Where possible, store the user's token in ~/.vault-token-SUFFIX
for safekeeping, where SUFFIX is the first 8 hex digits of the SHA-256
hash of host:port. If that can't be found, fall back to the
historical ~/.vault-token location.

Fixes #2092

Where possible, store the user's token in `~/.vault-token-SUFFIX`
for safekeeping, where `SUFFIX` is the first 8 hex digits of the SHA-256
hash of `host:port`.  If that can't be found, fall back to the
historical `~/.vault-token` location.

Fixes hashicorp#2092
@hashicorp-cla
Copy link

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

Have you signed the CLA already but the status is still pending? Recheck it.

@chrishoffman
Copy link
Contributor

Closing due to inactivity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support multiple Vault commandline client tokens
3 participants