A HashiCorp Vault UI written with VueJS and Vault native Go API
The deployment config file has slightly changed. The certificate information has been moved to its own struct. Check this wiki page for samples, or the sample config file
Goldfish now also accepts non-approle tokens for deployment. They still must be wrapped. The procedures for bootstrapping are identical, goldfish will determine whether the token is approle or not. The recommended bootstrap method is still an approle token, and therefore deployment instructions on wiki pages will remain in approle fashion.
issuing_ca
field, for a full certificate chainip_sans
and alt_names
fields to PKI integration (#223)common_name
field to PKI integrationSHA256 sum of binaries:
a716db6277afcac21a404b6155d0c52b1d633f27d39fba240aae4b9d67d70943
1a270bda441168e17d96952c78a24725ccd40c637b702e8e27e3ab5d664de10b
v0.8.0
brings some security updates and new features to the frontend.
Deployment steps remain the same.
Notes:
This is a release candidate only! Deployment steps remain the same.
Notes:
Deployment steps are unchanged. Simply change your URL's version number and redeploy.
v0.8.3
and up (#169)Deployment steps are unchanged. Simply change your URL's version number and redeploy.
This is a release candidate only! Deployment steps are unchanged
v0.7.0
brings an expanded requests system. Users can now request for:
Deployment steps are identical to that of v0.6.0
too many open files
error #149Users
page will no longer load the first page of tokens immediatelyv0.7.0
brings an expanded requests system. Users can now request for:
Deployment steps are identical to that of v0.6.0