Hi Will,
The HMAC cannot be decoded; this is on purpose. You can, however,
match against it -- that's what the sys/audit-hash endpoint is for.
You provide the audit path (for instance, the file backend defaults to
file, so sys/audit-hash/file) and perform a write, passing in the
string you want to match. The endpoint will give you that audit
backend's HMAC value for that string.
In 0.6.3+ the accessor is added to each request entry, and if
hmac_accessor is set to false, it will be in plaintext there too.
Best,
Jeff
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
>
https://www.hashicorp.com/community-guidelines.html. Behavior in violation
> of those guidelines may result in your removal from this mailing list.
>
> GitHub Issues:
https://github.com/hashicorp/vault/issues
> IRC: #vault-tool on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vault" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
vault-tool+...@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/vault-tool/3f8f91d1-8cdb-40e8-918e-74d7e6e7d8ab%40googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.