Document upper limit on Transit encryption size (#6014)
This commit is contained in:
parent
b002915af3
commit
0a97f95ff4
|
@ -385,6 +385,12 @@ will be returned.
|
|||
}
|
||||
```
|
||||
|
||||
!> Vault HTTP API imposes a maximum request size of 32MB to prevent a denial
|
||||
of service attack. This can be tuned per [`listener`
|
||||
block](/docs/configuration/listener/tcp.html) in the Vault server
|
||||
configuration.
|
||||
|
||||
|
||||
### Sample Request
|
||||
|
||||
```
|
||||
|
|
|
@ -144,6 +144,11 @@ the proper permission, it can use this secrets engine.
|
|||
for storing the encrypted ciphertext. When the caller wants the plaintext,
|
||||
it must provide the ciphertext back to Vault to decrypt the value.
|
||||
|
||||
!> Vault HTTP API imposes a maximum request size of 32MB to prevent a denial
|
||||
of service attack. This can be tuned per [`listener`
|
||||
block](/docs/configuration/listener/tcp.html) in the Vault server
|
||||
configuration.
|
||||
|
||||
1. Decrypt a piece of data using the `/decrypt` endpoint with a named key:
|
||||
|
||||
```text
|
||||
|
|
Loading…
Reference in New Issue