Token helpers
A token helper is an external program that Vault calls to save, retrieve or erase a saved token. The token helper could be a very simple script or a more complex program depending on your needs. The interface to the external token helper is extremely simple.
By default the Vault CLI provides a built in tool for authenticating with any
of the enabled authentication backends. Once authenticated, the CLI will store
the generated token on disk in the ~/.vault-token
file. By using a token helper,
this default functionality can be changed.
Configuration
To configure a token helper, edit (or create) the file ~/.vault
and add a line similar to:
You will need to use the fully qualified path to the token helper script. The script should be executable.
Developing a token helper
The interface to a token helper is extremely simple: the script is passed with one argument that could be get
, store
or erase
. If the argument is get
, the script should do whatever work it needs to do to retrieve the stored token and then print the token to STDOUT
. If the argument is store
, Vault is asking you to store the token. Finally, if the argument is erase
, your program should erase the stored token.
If your program succeeds, it should exit with status code 0. If it encounters an issue that prevents it from working, it should exit with some other status code. You should write a user-friendly error message to STDERR
. You should never write anything other than the token to STDOUT
, as Vault assumes whatever it gets on STDOUT
is the token.
Example token helper
This is an example token helper written in Ruby that stores and retrieves tokens in a json file called ~/.vault_tokens
. The key is the environment variable \$VAULT_ADDR, this allows the Vault user to easily store and retrieve tokens from a number of different Vault servers.