»Vault 1.7 Release Highlights
»Secrets Engine Enhancements
- Tokenization (Enterprise ADP Module): General Availability of a new transformation method for tokenizing sensitive data stored in un-trusted/semi-trusted systems. Tokenization is available as part of the “Advanced Data Protection” module in Vault Enterprise. Tokenization provides non-reversible data protection pursuant to requirements for data irreversibility (PCI-DSS, GDPR, etc.).
- Key Management Secrets Engine General Availability (Enterprise ADP Module): A new Key Management Secrets Engine to help manage and securely distribute keys to various cloud KMS services. This feature is to be used in conjunction with Microsoft’s Azure KeyVault (GA) and AWS KMS (Beta).
- UI for the Database Secrets Engine: A new UI to enable users to connect external databases to Vault (with initial support for MongoDB), set up dynamic roles, and generate dynamic and static credentials.
- Snowflake Secrets Engine: Snowflake support to the combined database secrets engine to manage static and dynamic credentials for the Snowflake platform.
- TFE/TFC Secrets Engine: New secrets engine to allow TFE/TFC users to generate short-lived ephemeral user/team or organization tokens credentials to be used in their pipelines.
- Active Directory Dynamic Credentials: Allows for creation of short lived AD accounts when using the OpenLDAP engine in "AD" mode.
»Storage Backend Enhancements
- Integrated Storage Autopilot: New autopilot enhancements to simplify and automate the cluster management operational experience. These include:
- Checks to monitor node health and status
- Server stabilization to prevent disruption to raft quorum due to an unstable new node
- Dead server cleanup to help maintain cluster stability For Vault Enterprise, autopilot will automatically include non-voter considerations to the above functionality.
- Aerospike Storage Backend: Support for using Aerospike as a community supported storage backend option.
»Security and Cryptography Enhancements
- Barrier Auto Key Rotation: Updates to allow Vault to automatically rotate to a new barrier key for future encryption after crossing the 2^32 encryption threshold, thereby improving security.
- KMIP Entropy Augmentation (Enterprise ADP Module): The ability to use entropy augmentation to generate KMIP certificates.
»Vault Metrics Enhancements
- Usage Metrics Visibility:
- Vault Auditor now includes the active KMIP certificate count as part of the client usage metrics.
- Added metrics for active entity count.
- Added API for partial month client count.
- Telemetry Metrics: Added new metrics related to lease expiration.
»Performance and Reliability Improvements
- Expiration Manager Improvements: Improved how Vault resources are consumed during lease revocations.
- Client Controlled Consistency (Enterprise): New options to use configurable headers to control the consistency of reads after writes to performance secondary clusters and performance standby nodes.
- Memory Utilization Improvements (Enterprise): The replication log buffer is now memory bound as well as length bound. This allows Vault to limit the memory footprint of the log buffer. The maximum size and length are now user configurable.
- Username Customization: Allows users to customize dynamically generated usernames.
- Add OTP Flag to Okta Login: Allows for a one-time password to be passed in along with the Okta login command for users who are unable to accept/respond to an Okta MFA push notification.
- Extension of Evaluation License (Enterprise): Extended the Vault Enterprise evaluation license from 30 minutes to 6 hours.
- Vault Agent Improvements:
- Vault Agent can now run as a Windows Service.
- Added support for an agent persistent cache to allow for a graceful handoff between init and sidecar containers when using vault-k8s (mutating admissions controller) for secrets injection.
- Operator enhancement: The Vault status command (which prints the current state of Vault including whether it is sealed and if HA mode is enabled) now works when a namespace is set.
- There is a known issue that may cause Autopilot to be unable to determine the leader node. This occurs if the IP in the raft peer list is different from the configured cluster address. If affected you should disable Autopilot by setting the VAULT_RAFT_AUTOPILOT_DISABLE environment variable to 1.
- Autopilot is not currently supported with Integrated Storage's HA-only mode or with DR secondary clusters.
For more detailed information, please refer to the Changelog.