Downloads:
257,043
Downloads of v 1.18.0:
764
Last Update:
10 Oct 2024
Package Maintainer(s):
Software Author(s):
- Mitchell Hashimoto
- HashiCorp
Tags:
vault hashicorp- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Vault
- 1
- 2
- 3
1.18.0 | Updated: 10 Oct 2024
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
257,043
Downloads of v 1.18.0:
764
Maintainer(s):
Software Author(s):
- Mitchell Hashimoto
- HashiCorp
Vault 1.18.0
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Mitchell Hashimoto, HashiCorp. The inclusion of Mitchell Hashimoto, HashiCorp trademark(s), if any, upon this webpage is solely to identify Mitchell Hashimoto, HashiCorp goods or services and not for commercial purposes.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Vault, run the following command from the command line or from PowerShell:
To upgrade Vault, run the following command from the command line or from PowerShell:
To uninstall Vault, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download vault --internalize --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade vault -y --source="'INTERNAL REPO URL'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade vault -y --source="'INTERNAL REPO URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install vault
win_chocolatey:
name: vault
version: '1.18.0'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'vault' do
action :install
source 'INTERNAL REPO URL'
version '1.18.0'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller vault
{
Name = "vault"
Version = "1.18.0"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'vault':
ensure => '1.18.0',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...
This package was approved as a trusted package on 10 Oct 2024.
Vault is a tool for securely accessing secrets. A secret is anything that you want to tightly control access to, such as API keys, passwords, certificates, and more. Vault provides a unified interface to any secret, while providing tight access control and recording a detailed audit log.
A modern system requires access to a multitude of secrets: database credentials, API keys for external services, credentials for service-oriented architecture communication, etc. Understanding who is accessing what secrets is already very difficult and platform-specific. Adding on key rolling, secure storage, and detailed audit logs is almost impossible without a custom solution. This is where Vault steps in.
The key features of Vault are:
- Secure Secret Storage: Arbitrary key/value secrets can be stored in Vault. Vault encrypts these secrets prior to writing them to persistent storage, so gaining access to the raw storage isn't enough to access your secrets. Vault can write to disk, Consul, and more.
- Dynamic Secrets: Vault can generate secrets on-demand for some systems, such as AWS or SQL databases. For example, when an application needs to access an S3 bucket, it asks Vault for credentials, and Vault will generate an AWS keypair with valid permissions on demand. After creating these dynamic secrets, Vault will also automatically revoke them after the lease is up.
- Data Encryption: Vault can encrypt and decrypt data without storing it. This allows security teams to define encryption parameters and developers to store encrypted data in a location such as SQL without having to design their own encryption methods.
- Leasing and Renewal: All secrets in Vault have a lease associated with it. At the end of the lease, Vault will automatically revoke that secret. Clients are able to renew leases via built-in renew APIs.
- Revocation: Vault has built-in support for secret revocation. Vault can revoke not only single secrets, but a tree of secrets, for example all secrets read by a specific user, or all secrets of a particular type. Revocation assists in key rolling as well as locking down systems in the case of an intrusion.
For more information, see the introduction section of the Vault website.
Log in or click on link to see number of positives.
- vault.1.18.0.nupkg (27fd00b460e3) - ## / 66
- vault_1.18.0_windows_amd64.zip (fb673aeb50be) - ## / 63
- vault_1.18.0_windows_386.zip (782564a59806) - ## / 63
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
Vault 1.18.0 | 764 | Thursday, October 10, 2024 | Approved | |
Vault 1.17.6 | 2880 | Thursday, September 26, 2024 | Approved | |
Vault 1.17.5 | 4183 | Saturday, August 31, 2024 | Approved | |
Vault 1.17.4 | 164 | Friday, August 30, 2024 | Approved | |
Vault 1.17.3 | 3577 | Thursday, August 8, 2024 | Approved | |
Vault 1.17.2 | 4699 | Thursday, July 11, 2024 | Approved | |
Vault 1.17.1 | 2029 | Thursday, June 27, 2024 | Approved | |
Vault 1.17.0 | 2272 | Thursday, June 13, 2024 | Approved | |
Vault 1.16.3 | 1913 | Thursday, May 30, 2024 | Approved | |
Vault 1.16.2 | 4569 | Wednesday, April 24, 2024 | Approved | |
Vault 1.16.1 | 2617 | Friday, April 5, 2024 | Approved | |
Vault 1.16.0 | 1431 | Wednesday, March 27, 2024 | Approved | |
Vault 1.15.6 | 4451 | Friday, March 1, 2024 | Approved | |
Vault 1.15.5 | 8051 | Wednesday, January 31, 2024 | Approved | |
Vault 1.15.4 | 21059 | Wednesday, December 6, 2023 | Approved | |
Vault 1.15.3 | 926 | Friday, December 1, 2023 | Approved | |
Vault 1.15.2 | 6055 | Thursday, November 9, 2023 | Approved | |
Vault 1.15.1 | 2981 | Thursday, October 26, 2023 | Approved | |
Vault 1.15.0 | 5346 | Wednesday, September 27, 2023 | Approved | |
Vault 1.14.3 | 2279 | Thursday, September 14, 2023 | Approved | |
Vault 1.14.2 | 1991 | Wednesday, August 30, 2023 | Approved | |
Vault 1.14.1 | 4156 | Wednesday, July 26, 2023 | Approved | |
Vault 1.14.0 | 4689 | Wednesday, June 21, 2023 | Approved | |
Vault 1.13.3 | 1605 | Friday, June 9, 2023 | Approved | |
Vault 1.13.2 | 13502 | Thursday, April 27, 2023 | Approved | |
Vault 1.13.1 | 4247 | Thursday, March 30, 2023 | Approved | |
Vault 1.13.0 | 1549 | Tuesday, March 7, 2023 | Approved | |
Vault 1.12.3 | 2141 | Thursday, February 23, 2023 | Approved | |
Vault 1.12.2 | 6000 | Saturday, December 17, 2022 | Approved | |
Vault 1.11.1 | 25004 | Wednesday, July 27, 2022 | Approved | |
Vault 1.11.0 | 2558 | Tuesday, June 21, 2022 | Approved | |
Vault 1.10.4 | 533 | Friday, June 17, 2022 | Approved | |
Vault 1.10.3 | 3372 | Friday, May 13, 2022 | Approved | |
Vault 1.10.2 | 63 | Friday, May 13, 2022 | Approved | |
Vault 1.10.1 | 1541 | Monday, April 25, 2022 | Approved | |
Vault 1.10.0 | 2332 | Friday, March 25, 2022 | Approved | |
Vault 1.9.4 | 1432 | Wednesday, March 9, 2022 | Approved | |
Vault 1.9.3 | 2358 | Monday, January 31, 2022 | Approved | |
Vault 1.9.2 | 1963 | Wednesday, December 22, 2021 | Approved | |
Vault 1.9.1 | 1104 | Tuesday, December 14, 2021 | Approved | |
Vault 1.9.0 | 1609 | Tuesday, November 23, 2021 | Approved | |
Vault 1.8.5 | 100 | Tuesday, November 23, 2021 | Approved | |
Vault 1.8.4 | 3130 | Friday, October 8, 2021 | Approved | |
Vault 1.8.3 | 687 | Friday, October 1, 2021 | Approved | |
Vault 1.8.2 | 714 | Thursday, September 30, 2021 | Approved | |
Vault 1.8.1 | 170 | Thursday, September 30, 2021 | Approved | |
Vault 1.8.0 | 3328 | Thursday, July 29, 2021 | Approved | |
Vault 1.7.3 | 2708 | Thursday, June 17, 2021 | Approved | |
Vault 1.7.2 | 1973 | Friday, May 21, 2021 | Approved | |
Vault 1.7.1 | 1559 | Monday, April 26, 2021 | Approved | |
Vault 1.7.0 | 1594 | Tuesday, April 6, 2021 | Approved | |
Vault 1.6.3 | 466 | Thursday, March 25, 2021 | Approved | |
Vault 1.6.2 | 4023 | Monday, February 1, 2021 | Approved | |
Vault 1.6.1 | 742 | Thursday, January 21, 2021 | Approved | |
Vault 1.5.5 | 5557 | Friday, October 23, 2020 | Approved | |
Vault 1.5.4 | 21898 | Thursday, October 22, 2020 | Approved | |
Vault 1.5.3 | 615 | Thursday, October 22, 2020 | Approved | |
Vault 1.5.2 | 2352 | Wednesday, August 26, 2020 | Approved | |
Vault 1.5.0 | 1688 | Wednesday, July 22, 2020 | Approved | |
Vault 1.4.3 | 909 | Friday, July 3, 2020 | Approved | |
Vault 1.4.1 | 1765 | Monday, May 4, 2020 | Approved | |
Vault 1.4.0 | 1409 | Thursday, April 9, 2020 | Approved | |
Vault 1.3.4 | 250 | Wednesday, April 8, 2020 | Approved | |
Vault 1.3.3 | 941 | Monday, March 9, 2020 | Approved | |
Vault 1.3.2 | 1511 | Friday, January 24, 2020 | Approved | |
Vault 1.3.1 | 1669 | Friday, December 20, 2019 | Approved | |
Vault 1.3.0 | 527 | Wednesday, December 11, 2019 | Approved | |
Vault 1.2.4 | 1047 | Tuesday, November 12, 2019 | Approved | |
Vault 1.2.3 | 3435 | Monday, September 16, 2019 | Approved | |
Vault 1.2.2 | 2376 | Friday, August 16, 2019 | Approved | |
Vault 1.2.1 | 196 | Thursday, August 8, 2019 | Approved | |
Vault 1.2.0 | 977 | Wednesday, July 31, 2019 | Approved | |
Vault 1.1.1 | 5093 | Tuesday, April 16, 2019 | Approved | |
Vault 1.1.0 | 1053 | Tuesday, March 19, 2019 | Approved | |
Vault 1.0.3 | 729 | Friday, March 1, 2019 | Approved | |
Vault 0.10.0 | 3153 | Monday, April 16, 2018 | Approved | |
Vault 0.10.0-rc1 | 323 | Saturday, April 7, 2018 | Approved | |
Vault 0.9.6 | 511 | Saturday, April 7, 2018 | Approved | |
Vault 0.9.5 | 294 | Saturday, April 7, 2018 | Approved | |
Vault 0.9.4 | 377 | Saturday, April 7, 2018 | Approved | |
Vault 0.9.3 | 318 | Saturday, April 7, 2018 | Approved | |
Vault 0.9.2 | 315 | Saturday, April 7, 2018 | Approved | |
Vault 0.9.1 | 1024 | Saturday, January 13, 2018 | Approved | |
Vault 0.9.0 | 390 | Saturday, January 13, 2018 | Approved | |
Vault 0.8.3 | 983 | Wednesday, September 20, 2017 | Approved | |
Vault 0.8.2 | 396 | Wednesday, September 20, 2017 | Approved | |
Vault 0.8.1 | 468 | Thursday, August 24, 2017 | Approved | |
Vault 0.8.0 | 466 | Thursday, August 24, 2017 | Approved | |
Vault 0.7.3 | 588 | Thursday, June 8, 2017 | Approved | |
Vault 0.7.2 | 448 | Wednesday, June 7, 2017 | Approved | |
Vault 0.7.1 | 407 | Wednesday, June 7, 2017 | Approved | |
Vault 0.7.0 | 427 | Wednesday, June 7, 2017 | Approved | |
Vault 0.6.5 | 952 | Wednesday, February 8, 2017 | Approved | |
Vault 0.6.4 | 563 | Thursday, December 22, 2016 | Approved | |
Vault 0.6.3 | 428 | Wednesday, December 14, 2016 | Approved | |
Vault 0.6.2 | 504 | Tuesday, October 25, 2016 | Approved | |
Vault 0.6.1 | 502 | Tuesday, August 30, 2016 | Approved |
HashiCorp 2015-2022
CHANGES:
- activity (enterprise): filter all fields in client count responses by the request namespace [GH-27790]
- activity (enterprise): remove deprecated fields distinct_entities and non_entity_tokens [GH-27830]
- activity log: Deprecated the field "default_report_months". Instead, the billing start time will be used to determine the start time
when querying the activity log endpoints. [GH-27350] - activity log: Deprecates the current_billing_period field for /sys/internal/counters/activity. The default start time
will automatically be set the billing period start date. [GH-27426] - activity: The activity export API now requires the
sudo
ACL capability. [GH-27846] - activity: The activity export API now responds with a status of 204 instead 400 when no data exists within the time range specified by
start_time
andend_time
. [GH-28064] - activity: The startTime will be set to the start of the current billing period by default.
The endTime will be set to the end of the current month. This applies to /sys/internal/counters/activity,
/sys/internal/counters/activity/export, and the vault operator usage command that utilizes /sys/internal/counters/activity. [GH-27379] - api: Update backoff/v3 to backoff/v4.3.0 [GH-26868]
- auth/alicloud: Update plugin to v0.19.0 [GH-28263]
- auth/azure: Update plugin to v0.19.0 [GH-28294]
- auth/cf: Update plugin to v0.18.0 [GH-27724]
- auth/cf: Update plugin to v0.19.0 [GH-28266]
- auth/gcp: Update plugin to v0.19.0 [GH-28366]
- auth/jwt: Update plugin to v0.21.0 [GH-27498]
- auth/jwt: Update plugin to v0.22.0 [GH-28349]
- auth/kerberos: Update plugin to v0.13.0 [GH-28264]
- auth/kubernetes: Update plugin to v0.20.0 [GH-28289]
- auth/oci: Update plugin to v0.17.0 [GH-28307]
- cli: The undocumented
-dev-three-node
and-dev-four-cluster
CLI options have been removed. [GH-27578] - consul-template: updated to version 0.39.1 [GH-27799]
- core(enterprise): Updated the following two control group related errors responses to respond with response code 400 instead of 500:
control group: could not find token
, andcontrol group: token is not a valid control group token
. - core: Bump Go version to 1.22.7
- database/couchbase: Update plugin to v0.12.0 [GH-28327]
- database/elasticsearch: Update plugin to v0.16.0 [GH-28277]
- database/mongodbatlas: Update plugin to v0.13.0 [GH-28268]
- database/redis-elasticache: Update plugin to v0.5.0 [GH-28293]
- database/redis: Update plugin to v0.4.0 [GH-28404]
- database/snowflake: Update plugin to v0.12.0 [GH-28275]
- sdk: Upgrade to go-secure-stdlib/[email protected], which also bumps github.com/docker/docker to v26.1.5+incompatible [GH-28269]
- secrets/ad: Update plugin to v0.19.0 [GH-28361]
- secrets/alicloud: Update plugin to v0.18.0 [GH-28271]
- secrets/azure: Update plugin to v0.19.2 [GH-27652]
- secrets/azure: Update plugin to v0.20.0 [GH-28267]
- secrets/gcp: Update plugin to v0.20.0 [GH-28324]
- secrets/gcpkms: Update plugin to v0.18.0 [GH-28300]
- secrets/gcpkms: Update plugin to v0.19.0 [GH-28360]
- secrets/kubernetes: Update plugin to v0.9.0 [GH-28287]
- secrets/kv: Update plugin to v0.20.0 [GH-28334]
- secrets/mongodbatlas: Update plugin to v0.13.0 [GH-28348]
- secrets/openldap: Update plugin to v0.14.0 [GH-28325]
- secrets/ssh: Add a flag,
allow_empty_principals
to allow keys or certs to apply to any user/principal. [GH-28466] - secrets/terraform: Update plugin to v0.10.0 [GH-28312]
- secrets/terraform: Update plugin to v0.9.0 [GH-28016]
- ui: Uses the internal/counters/activity/export endpoint for client count export data. [GH-27455]
FEATURES:
- AWS secrets engine STS session tags support: Adds support for setting STS
session tags when generating temporary credentials using the AWS secrets
engine. [GH-27620] - Adaptive Overload Protection (enterprise): Enables Adaptive Overload Protection
for write requests as a GA feature (enabled by default) for Integrated Storage. - Audit Entry Exclusion: Audit devices support excluding fields from entries being written to them, with expression-based rules (powered by go-bexpr) to determine when the specific fields are excluded.
- Workload Identity Federation UI for AWS (enterprise): Add WIF fields to AWS secrets engine. [GH-28148]
- KV v2 Patch/Subkey (enterprise): Adds GUI support to read the subkeys of a KV v2 secret and patch (partially update) secret data. [GH-28212]
- Self-Managed Static Roles: Self-Managed Static Roles are now supported for select SQL database engines (Postgres, Oracle). Requires Vault Enterprise. [GH-28199]
- Vault Minimal Version: Add the ability to build a minimal version of Vault
with only core features using the BUILD_MINIMAL environment variable. [GH-27394] - Vault PKI 3GPP CMPv2 Server (Enterprise): Support for the PKI 3GPP CMPv2 certificate management protocol has been added to the Vault PKI Plugin. This allows standard CMPv2 clients to request certificates from a Vault server with no knowledge of Vault APIs.
IMPROVEMENTS:
- activity log: Changes how new client counts in the current month are estimated, in order to return more
visibly sensible totals. [GH-27547] - activity: The activity export API can now be called in non-root namespaces. Resulting records will be filtered to include the requested namespace (via
X-Vault-Namespace
header or within the path) and all child namespaces. [GH-27846] - activity: The activity export API now includes identity metadata about entity clients. [GH-28064]
- activity:
/sys/internal/counters/activity
will now include a warning if the specified usage period contains estimated client counts. [GH-28068] - agent/sink: Allow configuration of the user and group ID of the file sink. [GH-27123]
- agent: Add metric (vault.agent.authenticated) that is set to 1 when vault agent has a valid token and zero if it does not. [GH-26570]
- agent: Add the ability to dump pprof to the filesystem using SIGUSR2 [GH-27510]
- audit: Adds TRACE logging to log request/response under certain circumstances, and further improvements to the audit subsystem. [GH-28056]
- audit: Ensure that any underyling errors from audit devices are logged even if we consider auditing to be a success. [GH-27809]
- audit: Internal implementation changes to the audit subsystem which improve performance. [GH-27952]
- audit: Internal implementation changes to the audit subsystem which improve relability. [GH-28286]
- audit: sinks (file, socket, syslog) will attempt to log errors to the server operational
log before returning (if there are errors to log, and the context is done). [GH-27859] - auth/cert: Cache full list of role trust information separately to avoid
eviction, and avoid duplicate loading during multiple simultaneous logins on
the same role. [GH-27902] - cli: Add a
--dev-no-kv
flag to prevent auto mounting a key-value secret backend when running a dev server [GH-16974] - cli: Allow vault CLI HTTP headers to be specified using the JSON-encoded VAULT_HEADERS environment variable [GH-21993]
- cli:
vault operator usage
will now include a warning if the specified usage period contains estimated client counts. [GH-28068] - core/activity: Ensure client count queries that include the current month return consistent results by sorting the clients before performing estimation [GH-28062]
- core/cli: Example 'help' pages for vault read / write docs improved. [GH-19064]
- core/identity: allow identity backend to be tuned using standard secrets backend tuning parameters. [GH-14723]
- core/metrics: ensure core HA metrics are always output to Prometheus. [GH-27966]
- core: log at level ERROR rather than INFO when all seals are unhealthy. [GH-28564]
- core: make authLock and mountsLock in Core configurable via the detect_deadlocks configuration parameter. [GH-27633]
- database/postgres: Add new fields to the plugin's config endpoint for client certificate authentication. [GH-28024]
- db/cassandra: Add
disable_host_initial_lookup
option to backend, allowing the disabling of initial host lookup. [GH-9733] - identity: alias metadata is now returned when listing entity aliases [GH-26073]
- license utilization reporting (enterprise): Auto-roll billing start date. [GH-27656]
- physical/raft: Log when the MAP_POPULATE mmap flag gets disabled before opening the database. [GH-28526]
- proxy/sink: Allow configuration of the user and group ID of the file sink. [GH-27123]
- proxy: Add the ability to dump pprof to the filesystem using SIGUSR2 [GH-27510]
- raft-snapshot (enterprise): add support for managed identity credentials for azure snapshots
- raft/autopilot: Persist Raft server versions so autopilot always knows the versions of all servers in the cluster. Include server versions in the Raft bootstrap challenge answer so autopilot immediately knows the versions of new nodes. [GH-28186]
- sdk/helper: Allow setting environment variables when using NewTestDockerCluster [GH-27457]
- secrets-sync (enterprise): add support for specifying the replication regions for secret storage within GCP Secret Manager destinations
- secrets-sync (enterprise): add support for syncing secrets to github environments within repositories
- secrets-sync (enterprise): add support for syncing secrets to github organizations (beta)
- secrets/database/hana: Update HANA db client to v1.10.1 [GH-27950]
- secrets/database: Add support for GCP CloudSQL private IP's. [GH-26828]
- secrets/pki: Key Usage can now be set on intermediate and root CAs, and CSRs generated by the PKI secret's engine. [GH-28237]
- secrets/pki: Track the last time auto-tidy ran to address auto-tidy not running if the auto-tidy interval is longer than scheduled Vault restarts. [GH-28488]
- serviceregistration: Added support for Consul ServiceMeta tags from config file from the new
service_meta
config field. [GH-11084] - storage/azure: Updated metadata endpoint to
GetMSIEndpoint
, which supports more than just the metadata service. [GH-10624] - storage/dynamodb: Speed up list and delete of large directories by only requesting keys from DynamoDB [GH-21159]
- storage/etcd: Update etcd3 client to v3.5.13 to allow use of TLSv1.3. [GH-26660]
- storage/raft: Bump raft to v1.7.0 which includes pre-vote. This should make clusters more stable during network partitions. [GH-27605]
- storage/raft: Improve autopilot logging on startup to show config values clearly and avoid spurious logs [GH-27464]
- ui/secrets-sync: Hide Secrets Sync from the sidebar nav if user does not have access to the feature. [GH-27262]
- ui: AWS credentials form sets credential_type from backing role [GH-27405]
- ui: Creates separate section for updating sensitive creds for Secrets sync create/edit view. [GH-27538]
- ui: For AWS and SSH secret engines hide mount configuration details in toggle and display configuration details or cta. [GH-27831]
- ui: Mask obfuscated fields when creating/editing a Secrets sync destination. [GH-27348]
- ui: Move secret-engine configuration create/edit from routing
vault/settings/secrets/configure/<backend>
tovault/secrets/<backend>/configuration/edit
[GH-27918] - ui: Remove deprecated
current_billing_period
from dashboard activity log request [GH-27559] - ui: Update the client count dashboard to use API namespace filtering and other UX improvements [GH-28036]
- ui: remove initial start/end parameters on the activity call for client counts dashboard. [GH-27816]
- ui: simplify the date range editing experience in the client counts dashboard. [GH-27796]
- website/docs: Added API documentation for Azure Secrets Engine delete role [GH-27883]
- website/docs: corrected invalid json in sample payload for azure secrets engine create/update role [GH-28076]
BUG FIXES:
- activity: The sys/internal/counters/activity endpoint will return current month data when the end_date parameter is set to a future date. [GH-28042]
- agent: Fixed an issue causing excessive CPU usage during normal operation [GH-27518]
- auth/appid, auth/cert, auth/github, auth/ldap, auth/okta, auth/radius, auth/userpass: fixed an issue with policy name normalization that would prevent a token associated with a policy containing an uppercase character to be renewed. [GH-16484]
- auth/aws: fixes an issue where not supplying an external id was interpreted as an empty external id [GH-27858]
- auth/cert: During certificate validation, OCSP requests are debug logged even if Vault's log level is above DEBUG. [GH-28450]
- auth/cert: Merge error messages returned in login failures and include error when present [GH-27202]
- auth/cert: Use subject's serial number, not issuer's within error message text in OCSP request errors [GH-27696]
- auth/cert: When using ocsp_ca_certificates, an error was produced though extra certs validation succeeded. [GH-28597]
- auth/cert: ocsp_ca_certificates field was not honored when validating OCSP responses signed by a CA that did not issue the certificate. [GH-28309]
- auth/token: Fix token TTL calculation so that it uses
max_lease_ttl
tune value for tokens created viaauth/token/create
. [GH-28498] - auth/token: fixes an edge case bug that "identity_policies" is nil and causes cli vault login error [GH-17007]
- auth: Updated error handling for missing login credentials in AppRole and UserPass auth methods to return a 400 error instead of a 500 error. [GH-28441]
- cli: Fixed an erroneous warning appearing about
-address
not being set when it is. [GH-27265] - cli: Fixed issue with
vault hcp connect
where HCP resources with uppercase letters were inaccessible when entering the correct project name. [GH-27694] - command: The
vault secrets move
andvault auth move
command will no longer attempt to write to storage on performance standby nodes. [GH-28059] - config: Vault TCP listener config now correctly supports the documented proxy_protocol_behavior
setting of 'deny_unauthorized' [GH-27459] - core (enterprise): Fix 500 errors that occurred querying
sys/internal/ui/mounts
for a mount prefixed by a namespace path when path filters are configured. [GH-27939] - core (enterprise): Fix HTTP redirects in namespaces to use the correct path and (in the case of event subscriptions) the correct URI scheme. [GH-27660]
- core (enterprise): Fix deletion of MFA login-enforcement configurations on standby nodes
- core/audit: Audit logging a Vault request/response checks if the existing context
is cancelled and will now use a new context with a 5 second timeout.
If the existing context is cancelled a new context, will be used. [GH-27531] - core/config: fix issue when using
proxy_protocol_behavior
withdeny_unauthorized
,
which causes the Vault TCP listener to close after receiving an untrusted upstream proxy connection. [GH-27589] - core/identity: Fixed an issue where deleted/reassigned entity-aliases were not removed from in-memory database. [GH-27750]
- core/seal (enterprise): Fix bug that caused seal generation information to be replicated, which prevented disaster recovery and performance replication clusters from using their own seal high-availability configuration.
- core: Fixed an issue where maximum request duration timeout was not being added to all requests containing strings sys/monitor and sys/events. With this change, timeout is now added to all requests except monitor and events endpoint. [GH-28230]
- core: Fixed an issue with performance standbys not being able to handle rotate root requests. [GH-27631]
- database/postgresql: Fix potential error revoking privileges in postgresql database secrets engine when a schema contains special characters [GH-28519]
- databases: fix issue where local timezone was getting lost when using a rotation schedule cron [GH-28509]
- helper/pkcs7: Fix parsing certain messages containing only certificates [GH-27435]
- identity/oidc: prevent JWKS from being generated by multiple concurrent requests [GH-27929]
- licensing (enterprise): fixed issue where billing start date might not be correctly updated on performance standbys
- proxy/cache (enterprise): Fixed a data race that could occur while tracking capabilities in Proxy's static secret cache. [GH-28494]
- proxy/cache (enterprise): Fixed an issue where Proxy with static secret caching enabled would not correctly handle requests to older secret versions for KVv2 secrets. Proxy's static secret cache now properly handles all requests relating to older versions for KVv2 secrets. [GH-28207]
- proxy/cache (enterprise): Fixed an issue where Proxy would not correctly update KV secrets when talking to a perf standby. Proxy will now attempt to forward requests to update secrets triggered by events to the active node. Note that this requires
allow_forwarding_via_header
to be configured on the cluster. [GH-27891] - proxy/cache (enterprise): Fixed an issue where cached static secrets could fail to update if the secrets belonged to a non-root namespace. [GH-27730]
- proxy: Fixed an issue causing excessive CPU usage during normal operation [GH-27518]
- raft/autopilot: Fixed panic that may occur during shutdown [GH-27726]
- replication (enterprise): fix cache invalidation issue leading to namespace custom metadata not being shown correctly on performance secondaries
- secrets-sync (enterprise): Destination set/remove operations will no longer be blocked as "purge in progress" after a purge job ended in failure.
- secrets-sync (enterprise): Fix KV secret access sometimes being denied, due to a double forward-slash (
//
) in the mount path, when the token should otherwise have access. - secrets-sync (enterprise): Normalize custom_tag keys and values for recoverable invalid characters.
- secrets-sync (enterprise): Normalize secret key names before storing the external_name in a secret association.
- secrets-sync (enterprise): Patching github sync destination credentials will properly update and save the new credentials.
- secrets-sync (enterprise): Properly remove tags from secrets in AWS when they are removed from the source association
- secrets-sync (enterprise): Return an error immediately on destination creation when providing invalid custom_tags based on destination type.
- secrets-sync (enterprise): Return more accurate error code for invalid connection details
- secrets-sync (enterprise): Secondary nodes in a cluster now properly check activation-flags values.
- secrets-sync (enterprise): Skip invalid GitHub repository names when creating destinations
- secrets-sync (enterprise): Validate corresponding GitHub app parameters
app_name
andinstallation_id
are set - secrets/database: Skip connection verification on reading existing DB connection configuration [GH-28139]
- secrets/identity (enterprise): Fix a bug that can cause DR promotion to fail in rare cases where a PR secondary has inconsistent alias information in storage.
- secrets/pki: fix lack of serial number to a certificate read resulting in a server side error. [GH-27681]
- secrets/transit (enterprise): Fix an issue that caused input data be returned as part of generated CMAC values.
- storage/azure: Fix invalid account name initialization bug [GH-27563]
- storage/raft (enterprise): Fix issue with namespace cache not getting cleared on snapshot restore, resulting in namespaces not found in the snapshot being inaccurately represented by API responses. [GH-27474]
- storage/raft: Fix auto_join not working with mDNS provider. [GH-25080]
- sys: Fix a bug where mounts of external plugins that were registered before Vault v1.0.0 could not be tuned to
use versioned plugins. [GH-27881] - ui: Allow creation of session_token type roles for AWS secret backend [GH-27424]
- ui: Display an error and force a timeout when TOTP passcode is incorrect [GH-27574]
- ui: Ensure token expired banner displays when batch token expires [GH-27479]
- ui: Fix UI improperly checking capabilities for enabling performance and dr replication [GH-28371]
- ui: Fix cursor jump on KVv2 json editor that would occur after pressing ENTER. [GH-27569]
- ui: fix
default_role
input missing from oidc auth method configuration form [GH-28539] - ui: fix issue where enabling then disabling "Tidy ACME" in PKI results in failed API call. [GH-27742]
- ui: fix namespace picker not working when in small screen where the sidebar is collapsed by default. [GH-27728]
- ui: fixes renew-self being called right after login for non-renewable tokens [GH-28204]
- ui: fixes toast (flash) alert message saying "created" when deleting a kv v2 secret [GH-28093]
This package has no dependencies.
Ground Rules:
- This discussion is only about Vault and the Vault package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Vault, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.