Closed kenbreeman closed 9 years ago
Everything else appears to be working, I can read and write secrets
Vault is running as the root user (this is a test host) with the following command line:
vault server -config /etc/vault.cfg -log-level=debug
Audit log permissions:
> ls -la /var/log/vault_audit.log
-rw------- 1 root root 10927 Jun 4 20:58 /var/log/vault_audit.log
@armon So the Data
field of a response is map[string]interface{}
to allow for rich structures, but not for Go types (since it has to turn into an HTTP field anyways). The audit hashing doesn't expect this, since it expects to hash only primitives, in the case of a response (things that can go over JSON).
I think we need to change the sys/key-status
endpoint in vault/logical_system.go
to properly return the non-rich Time type, probably just a UTC timestamp.
Fixed by #373
I have vault deployed on kubernetes cluster with vault dev server enabled, helm install --name=vault \
--set 'ui.enabled=true' --set 'server.affinity=' \ --set 'authDelegator.enabled=true' vault-helm But then, when I deploy the application to read the secrets I am getting an Internal server error
Ran 'vault key-status' a couple of times using the 'file' backend and got a 500 error. I had run various cli commands prior to this including:
Command:
Version:
Config:
Log:
Audit log:
Filesystem: