pilgrim2go / goldfish

A HashiCorp Vault UI panel written with VueJS and Vault native Go API

Goldfish Vault UI - Live Demo

Show support for development by starring this repo!

What is this?

Goldfish is a HashiCorp Vault UI

Goldfish answers many auditing and administration questions that Vault API can't:

• Right now, are there any root tokens in Vault?
• Which policies, users, and tokens can access this particular secret path?
• The unseal admins are working from home, but we need a policy changed.
  • How do we do generate a root token only for this change, and make sure it's revoked after?
  • [Optional] Send the changeID to a slack channel, so admins can pull up the details and approve/reject
• Coming soon If I remove this secret/policy, will anybody's workflow break?

Running goldfish in production

See: Production Deployment

Features

• Hot-loadable server settings from a provided vault endpoint
• Displaying a vault endpoint as a 'bulletin board' in homepage
• Logging in with token, userpass, or github
• Secret Reading/editing/creating/listing
• Auth Searching/creating/listing/deleting
• Mounts Listing
• Policies Searching/Listing
• Encrypting and decrypting arbitrary strings using transit backend

Planned major features: Soon^TM

• DONE! Searching tokens by policy
  • E.g. Display all tokens that have the policy 'admins'
• DONE! Searching policy by rule
  • E.g. Display all policies that can access 'secret/data*'
• DONE! Request & approval based policy changes
  • Users can place a policy change request in vault
  • Admins must then provide unseal tokens for that specific request
  • Upon reaching a set number, goldfish generates a root token, performs edit, and revokes the root token
• Resource dependency chain
  • E.g. Will removing a particular policy affect current users?
• SAML to LDAP integration
• Secret backend specific tools (e.g. AWS backend)

Screenshots

Developing or testing goldfish

Running locally

You'll need go (v1.8), npm (>=3), and nodejs (>=5).

go get github.com/caiyeon/goldfish
cd $GOPATH/src/github.com/caiyeon/goldfish

# you'll need a vault instance. Force a root token for consistency
vault server -dev -dev-root-token-id=goldfish &
export VAULT_ADDR=http://127.0.0.1:8200
export VAULT_TOKEN=goldfish

# this transit key is needed to encrypt/decrypt user credentials
vault mount transit
vault write -f transit/keys/goldfish

# see vagrant/policies/goldfish.hcl for the required policy.
# transit key is not changable, but the secret path containing run-time settings can be changed
vault policy-write goldfish vagrant/policies/goldfish.hcl

# goldfish launches strictly from approle, because passing a token that humans can see would be silly
vault auth-enable approle
vault write auth/approle/role/goldfish role_name=goldfish secret_id_ttl=5m token_ttl=480h \
token_max_ttl=720h secret_id_num_uses=1 policies=default,goldfish
vault write auth/approle/role/goldfish/role-id role_id=goldfish

# build the backend server
go install

# run backend server with secret_id generated from approle
# -dev arg skips reading settings from vault and uses a default set
goldfish -dev -vault_token $(vault write -f -wrap-ttl=20m \
-format=json auth/approle/role/goldfish/secret-id \
| jq -r .wrap_info.token)

# run frontend in dev mode (with hot reload)
cd frontend
sudo npm install -g cross-env
npm install
npm run dev

# a browser window/tab should open, pointing directly to goldfish

# "-dev" disables many security standards. DO NOT USE -dev IN PRODUCTION!

Using a VM

While go and npm works decently on Windows, there is a one-line solution to spinning up a VM which will contain a dev vault instance and goldfish with hot-reload.

You'll need Vagrant and VirtualBox. On Windows, a restart after installation is needed.

# if you wish to launch goldfish in a VM:
git clone https://github.com/Caiyeon/goldfish.git
cd goldfish/vagrant

# this will take awhile
vagrant up --provision

# open up localhost:8001 in chrome on your local machine. You can login with token 'goldfish'

Configuration

Goldfish reads most of its configuration details from a provided vault endpoint (set by a cmd line arg config_path when launching the server)

There are several keys that are used:

DefaultSecretPath: the path that is loaded by default on Secrets page

TransitBackend: the transit backend that goldfish will use for encryption/decryption

ServerTransitKey: the key in TransitBackend used to encrypt/decrypt user credentials. Control this tightly (preferably, only allow goldfish to access this)

UserTransitKey: the key in TransitBackend used by Transit page. Individual users must be granted access to this in order to use the tool.

Development

Goldfish is being actively maintained (with new features every 1-2 weeks).

Contributions are welcomed. Feel free to pick up an issue and make a pull request, or open a new issue for a feature enhancement.

The Vagrant setup should provide a consistent dev environment.

Components

Frontend:

• VueJS
• Bulma CSS
• Vue Admin

Backend:

• Vault API wrapper

Design

See: Architecture

Why 'Goldfish'?

This server should behave as a goldfish, forgetting everything immediately after a request is completed. That, and other inside-joke reasons.

Credits for the goldfish icon goes to Laurel Chan