mirror of
https://github.com/hashicorp/vault.git
synced 2026-05-28 04:10:44 -04:00
changelog++
This commit is contained in:
parent
615945a6b0
commit
a4d535c9c1
1 changed files with 14 additions and 0 deletions
14
CHANGELOG.md
14
CHANGELOG.md
|
|
@ -10,6 +10,20 @@ DEPRECATIONS/CHANGES:
|
|||
allowing `list` capability must be carefully checked to ensure that they
|
||||
contain a trailing slash; some policies may need to be split into multiple
|
||||
stanzas to accommodate.
|
||||
* PKI Defaults to Unleased Certificates: When issuing certificates from the
|
||||
PKI backend, by default, no leases will be issued. If you want to manually
|
||||
revoke a certificate, its serial number can be used with the `pki/revoke`
|
||||
endpoint. Issuing leases is still possible by enabling the `generate_lease`
|
||||
toggle in PKI role entries (this will default to `true` for upgrades, to
|
||||
keep existing behavior), which will allow using lease IDs to revoke
|
||||
certificates. For installations issuing large numbers of certificates (tens
|
||||
to hundreds of thousands, or millions), this will significantly improve
|
||||
Vault startup time since leases associated with these certificates will not
|
||||
have to be loaded; however note that it also means that revocation of a
|
||||
token used to issue certificates will no longer add these certificates to a
|
||||
CRL. If this behavior is desired or needed, consider keeping leases enabled
|
||||
and ensuring lifetimes are reasonable, and issue long-lived certificates via
|
||||
a different role with leases disabled.
|
||||
|
||||
IMPROVEMENTS:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue