Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Audit broken in 0.7.1 #2687

Closed
tehmaze opened this issue May 8, 2017 · 1 comment
Closed

Audit broken in 0.7.1 #2687

tehmaze opened this issue May 8, 2017 · 1 comment

Comments

@tehmaze
Copy link

tehmaze commented May 8, 2017

Since the upgrade from 0.7.0 to 0.7.1 we ran into the following issue:

client$ VAULT_TOKEN=<redacted> vault token-lookup
error looking up token: Error making API request.

URL: GET https://vault.example.com:8200/v1/auth/token/lookup-self
Code: 500. Errors:

* internal error

The Vault daemon reports:

May 08 15:26:30 vault-101.example.com vault[53455]: 2017/05/08 15:26:30.836345 [ERROR] audit: panic during logging: request_path=auth/token/lookup-self error="reflect: reflect.Value.Set using value obtained using unexported field"
May 08 15:26:30 vault-101.example.com vault[53455]: 2017/05/08 15:26:30.836397 [ERROR] core: failed to audit response: request_path=auth/token/lookup-self error=panic generating audit log

Using the root token still works:

server# vault token-lookup | grep '^path'
path            	auth/token/root

Enabled audit backend:

server# vault audit-list
Path   Type  Description  Replication Behavior  Options

file/ file replicated file_path=/var/log/vault/audit.log

If we disable audit logging, the 500 for the client disappears:

server# vault audit-disable file
Successfully disabled audit backend 'file' if it was enabled
client$ VAULT_TOKEN=<redacted> vault token-lookup | grep '^path'
path            	auth/token/create

Also when we enable the syslog backend, the client receives a 500 and the same error is reported by the Vault daemon.

@jefferai
Copy link
Member

jefferai commented May 8, 2017

Hi @tehmaze ,

We've confirmed this. We're going to fix it and roll a new release. Thanks for the report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants