Hashicorp Vault – Install Client (CLI/GUI)

Hashicorp Vault has a variety of ways to access it. You can access it via a CLI client, via the rest api/CURL, and via a third party GUI client.

Intalling the CLI Client

Start by downloading the appropriate client for your platform from here:
https://www.vaultproject.io/downloads.html

OSX
Copy the downloaded bin file to the /usr/local/bin folder on your local machine
Create a system variable called VAULT_ADDR and set the path to the vault server.

  1. Open a terminal window
  2. type cd ~
  3. type vi .bash_profile
  4. Press i
  5. add the following: export VAULT_ADDR=https://myvaultserver.mydomain.com:8200
  6. Press Esc
  7. Type :wq
  8. Restart terminal

 

Windows
After exe file is downloaded, copy it to the C:\windows\system32 folder on your local machine

Create a system variable called VAULT_ADDR and set the path to the vault server.

  1. Open administrator command prompt
  2. setx VAULT_ADDR “https://myvaultserver.mydomain.com:8200”
  3. Restart Command Prompt

Installing GUI client

Hashicorp does not provide a GUI client with the free version of Vault. But third partieis have created their own using the vault API. My favorite GUI client can be downloaded here:
https://github.com/djenriquez/vault-ui/releases

Download the latest release for your platform, install it and then launch it.

After you launch you need to select the appropriate Authentication method, and input the path to your vault server. This is the same path that you used when configuring the CLI client above.

You can also install using a docker image. The docker images are generally more up to date than what you can find on the releases page on github. The docker image can be found here:
https://hub.docker.com/r/djenriquez/vault-ui/

If you decide to go the docker route, you will access the vault GUI via a web browser. Given that you can access it via a web browser, this really gives you a third Client option which is a web client.

Keep in mind that the docker image does not run HTTPS by default. So you will need to either work out how to add HTTPS to the docker image. Or you can put it behind a load balancer, and have the load balancer handle the HTTPS for you.