backport of commit 698c39f988f773040868cff8a38b76de03199a2d (#21089)

Co-authored-by: Jason O'Donnell <2160810+jasonodonnell@users.noreply.github.com>
This commit is contained in:
hc-github-team-secure-vault-core 2023-06-08 15:59:37 -04:00 committed by GitHub
parent 03a8d1268a
commit 860b92d02c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 28 additions and 0 deletions

View File

@ -199,3 +199,17 @@ vault write auth/ldap/config max_page_size=-1
#### Impacted Versions
Affects Vault 1.12.6.
### Slow Startup Time When Storing PKI Certificates
There was a regression introduced in 1.12.0 where Vault is slow to start because the
PKI secret engine performs a list operation on the stored certificates. If a large number
of certificates are stored this can cause long start times on active and standby nodes.
There is currently no workaround for this other than limiting the number of certificates stored
in Vault via the [PKI tidy](/vault/api-docs/secret/pki.mdx#tidy) or using `no_store`
flag for [PKI roles](/vault/api-docs/secret/pki.mdx#createupdate-role).
#### Impacted Versions
Affects Vault 1.12.0+

View File

@ -141,3 +141,17 @@ Affects Vault 1.13.0 to 1.13.2. Fixed in 1.13.3.
On upgrade, all local revocations will be synchronized between
clusters; revocation requests are not persisted when failing to
write cross-cluster.
### Slow Startup Time When Storing PKI Certificates
There was a regression introduced in 1.13.0 where Vault is slow to start because the
PKI secret engine performs a list operation on the stored certificates. If a large number
of certificates are stored this can cause long start times on active and standby nodes.
There is currently no workaround for this other than limiting the number of certificates stored
in Vault via the [PKI tidy](/vault/api-docs/secret/pki.mdx#tidy) or using `no_store`
flag for [PKI roles](/vault/api-docs/secret/pki.mdx#createupdate-role).
#### Impacted Versions
Affects Vault 1.13.0+