A beautiful way to manage your secrets in Vault
Configuration is accessed by clicking on the configuration cog on the login page.
Users can enter in the full endpoint to Vault, including scheme.
There are currently three supported authentication backends. Github, Username and Password, and Token.
By default, secrets will display as their raw JSON value represented by the data
field in the HTTP GET response metadata. However, users can apply a "Root Key" bias to the secrets through the settings page. The "Root Key" will be used when reading, creating and updating secrets such that the value displayed in the UI is the value stored at the "Root Key". For example, if the secret at secret/hello
is { "value": "world" }
, applying the "Root Key" value
will update the UI such that the secret will display as simply "world" instead of { "value": "world" }
.
Policies can be entered in as JSON or as HCL. If entered in as HCL, it will be converted to JSON as required for the PUT command in Vault's API. However, existing policies that are in HCL will continue to be displayed in HCL.
Vault-UI is attached to an automated build on Docker Hub. To run Vault-UI:
docker run -d \
-p 8000:8000 \
--name vault-ui \
djenriquez/vault-ui
In the case that you need to skip TLS verification, say for self-signed certs, you can run Vault-UI with the environment variable NODE_TLS_REJECT_UNAUTHORIZED=0
:
docker run -d \
-p 8000:8000 \
-e NODE_TLS_REJECT_UNAUTHORIZED=0 \
--name vault-ui \
djenriquez/vault-ui
npm install
# If you do not have webpack installed globally
npm install -g webpack
npm start
webpack -w
Vault-UI is licensed under BSD 2-Clause. See LICENSE for the full license text.