mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-16 11:37:04 +02:00
fix formatting for note in audit section (#17335)
This commit is contained in:
parent
9e11987f71
commit
e56c075c2b
@ -32,7 +32,7 @@ unique identifier assigned to each request.
|
|||||||
|
|
||||||
Most strings contained within requests and responses are hashed with a salt using HMAC-SHA256. The purpose of the hash is so that secrets aren't in plaintext within your audit logs. However, you're still able to check the value of secrets by generating HMACs yourself; this can be done with the audit device's hash function and salt by using the `/sys/audit-hash` API endpoint (see the documentation for more details).
|
Most strings contained within requests and responses are hashed with a salt using HMAC-SHA256. The purpose of the hash is so that secrets aren't in plaintext within your audit logs. However, you're still able to check the value of secrets by generating HMACs yourself; this can be done with the audit device's hash function and salt by using the `/sys/audit-hash` API endpoint (see the documentation for more details).
|
||||||
|
|
||||||
~>** Note:** Currently, only strings that come from JSON or returned in JSON are
|
~> Currently, only strings that come from JSON or returned in JSON are
|
||||||
HMAC'd. Other data types, like integers, booleans, and so on, are passed
|
HMAC'd. Other data types, like integers, booleans, and so on, are passed
|
||||||
through in plaintext. We recommend that all sensitive data be provided as string values
|
through in plaintext. We recommend that all sensitive data be provided as string values
|
||||||
inside all JSON sent to Vault (i.e., that integer values are provided in quotes).
|
inside all JSON sent to Vault (i.e., that integer values are provided in quotes).
|
||||||
|
Loading…
Reference in New Issue
Block a user