vault-token-helper | Hashicorp Vault Token Helper for macOS , Linux and Windows | Identity Management library

by joemiller Go Version: v0.3.7 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | vault-token-helper Summary

vault-token-helper is a Go library typically used in Security, Identity Management applications. vault-token-helper has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

A @hashicorp Vault [token helper] with support for native secret storage on macOS, Linux, and Windows.

Support

Quality

Security

License

Reuse

Support

vault-token-helper has a low active ecosystem.

It has 83 star(s) with 10 fork(s). There are 1 watchers for this library.

It had no major release in the last 12 months.

There are 4 open issues and 5 have been closed. On average issues are closed in 121 days. There are 6 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of vault-token-helper is v0.3.7

Quality

vault-token-helper has 0 bugs and 0 code smells.

Security

vault-token-helper has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

vault-token-helper code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

vault-token-helper is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

vault-token-helper releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 864 lines of code, 36 functions and 18 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed vault-token-helper and discovered the below as its top functions. This is intended to give you an instant insight into vault-token-helper implemented functionality, and help decide if they suit your requirements.

extendedList lists all the tokens in the backend .
initBackend initializes the keyring
initConfig initializes config file .
initDefaultConfig initializes the default configuration .
New returns a new keyring
encodeVaultAddr is used to encode the vault address string
AvailableBackends returns a list of available backends
Execute runs the root command
Erase removes an entry from the store .
decodeVaultAddr decodes an encoded string to url

Get all kandi verified functions for this library.

vault-token-helper Key Features

No Key Features are available at this moment for vault-token-helper.

vault-token-helper Examples and Code Snippets

No Code Snippets are available at this moment for vault-token-helper.

Community Discussions

Trending Discussions on vault-token-helper

Vault Token Helper not being detected?

QUESTION

Vault Token Helper not being detected?

Asked 2018-Jun-22 at 14:59

Problem:

I have three files in a vault:0.10.2 docker image at the following locations:

/home/myuser/token_helper: A token helper binary in Go that implements the token helper interface according to this documentation

/home/myuser/vault_start: A Go script that runs os.exec("vault", "operator", "init") and os.exec("vault", "server", "-config=myconfig.hcl")

/home/myuser/.vault: The token helper config file specifying the token helper binary location, and I've exported VAULT_CONFIG_PATH to point to this path. The file reads token_helper = "/home/myuser/token_helper".

The problem I'm seeing is while running the vault_start script, I get the following error:

...

ANSWER

Answered 2018-Jun-22 at 14:59

Figured this out, it was because the os.exec("vault", "operator", "init") line did not inherit the VAULT_CONFIG_PATH variable setting from the host, and so it was empty.

The following shows how to give os.Exec environment variables during it's run:

Source https://stackoverflow.com/questions/50956982

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install vault-token-helper

Configure Vault to use the token helper. This will create the ~/.vault config file:.
| OS | Command | |---------------------------------|--------------------------------------------------| | macOS | brew install joemiller/taps/vault-token-helper | | Linux<br>(LinuxBrew) untested | brew install joemiller/taps/vault-token-helper |.
| OS | Arch | binary | |---------|-------|---------------------------------------| | macOS | amd64 | [vault-token-helper][latest-binaries] | | Linux | amd64 | [vault-token-helper][latest-binaries] | | Windows | amd64 | [vault-token-helper][latest-binaries] |. [latest-binaries]: https://github.com/joemiller/vault-token-helper/releases/latest [rpm]: https://github.com/joemiller/vault-token-helper/releases/latest [deb]: https://github.com/joemiller/vault-token-helper/releases/latest.

Support

Please open a GitHub [issue](https://github.com/joemiller/vault-token-helper/issues). Setting the KEYRING_DEBUG environment variable to any value will produce additional output that may be useful for debugging common issues. Please set this variable and then run a command such as vault-token-helper list. Include the debug output in your issue.

Find more information at: