mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-31 11:31:07 +02:00
a43e292424
* conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
65 lines
1.8 KiB
Markdown
65 lines
1.8 KiB
Markdown
---
|
||
layout: "api"
|
||
page_title: "/sys/audit-hash - HTTP API"
|
||
sidebar_title: "<tt>/sys/audit-hash</tt>"
|
||
sidebar_current: "api-http-system-audit-hash"
|
||
description: |-
|
||
The `/sys/audit-hash` endpoint is used to hash data using an audit device's
|
||
hash function and salt.
|
||
---
|
||
|
||
# `/sys/audit-hash`
|
||
|
||
The `/sys/audit-hash` endpoint is used to calculate the hash of the data used by
|
||
an audit device's hash function and salt. This can be used to search audit logs
|
||
for a hashed value when the original value is known.
|
||
|
||
## Calculate Hash
|
||
|
||
This endpoint hashes the given input data with the specified audit device's
|
||
hash function and salt. This endpoint can be used to discover whether a given
|
||
plaintext string (the `input` parameter) appears in the audit log in obfuscated
|
||
form.
|
||
|
||
The audit log records requests and responses. Since the Vault API is JSON-based,
|
||
any binary data returned from an API call (such as a DER-format certificate) is
|
||
base64-encoded by the Vault server in the response. As a result such information
|
||
should also be base64-encoded to supply into the `input` parameter.
|
||
|
||
| Method | Path | Produces |
|
||
| :----- | :---------------------- | :----------------- |
|
||
| `POST` | `/sys/audit-hash/:path` | `204 (empty body)` |
|
||
|
||
### Parameters
|
||
|
||
- `path` `(string: <required>)` – Specifies the path of the audit device to
|
||
generate hashes for. This is part of the request URL.
|
||
|
||
- `input` `(string: <required>)` – Specifies the input string to hash.
|
||
|
||
### Sample Payload
|
||
|
||
```json
|
||
{
|
||
"input": "my-secret-vault"
|
||
}
|
||
```
|
||
|
||
### Sample Request
|
||
|
||
```
|
||
$ curl \
|
||
--header "X-Vault-Token: ..." \
|
||
--request POST \
|
||
--data @payload.json \
|
||
http://127.0.0.1:8200/v1/sys/audit-hash/example-audit
|
||
```
|
||
|
||
### Sample Response
|
||
|
||
```json
|
||
{
|
||
"hash": "hmac-sha256:08ba35..."
|
||
}
|
||
```
|