Downloads of v 1.7.1:


Last Update:

26 Apr 2021

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp


vault hashicorp


  • 1
  • 2
  • 3

1.7.1 | Updated: 26 Apr 2021



Downloads of v 1.7.1:



Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

  • 1
  • 2
  • 3
Vault 1.7.1

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


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:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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 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

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade vault -y --source="'STEP 3 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="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure vault installed
    name: vault
    state: present
    version: 1.7.1
    source: STEP 3 URL

See docs at

chocolatey_package 'vault' do
  action    :install
  version  '1.7.1'
  source   'STEP 3 URL'

See docs at

    Name: vault,
    Version: 1.7.1,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller vault
   Name     = 'vault'
   Ensure   = 'Present'
   Version  = '1.7.1'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'vault':
  provider => 'chocolatey',
  ensure   => '1.7.1',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install vault version="1.7.1" source="STEP 3 URL"

See docs at

5. 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 26 Apr 2021.


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.

$packageArgs = @{
  PackageName         = "vault"
  Url                 = "$($version)/vault_$($version)"
  UnzipLocation       = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
  Url64               = "$($version)/vault_$($version)"
  Checksum            = '4c22bd540b8dd132152fdd5db4929e67b8170939e71287e972b33d8ea777cc7a'
  ChecksumType        = 'sha256'
  Checksum64          = 'eab310b4e950a169e5dca54813043827940c66c42e5f8bc8d52a40417dedeae5'
  version             = '1.7.1'  

Install-ChocolateyZipPackage @packageArgs

Log in or click on link to see number of positives.

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.

Version Downloads Last Updated Status
Vault 1.7.0 1232 Tuesday, April 6, 2021 Approved
Vault 1.6.3 386 Thursday, March 25, 2021 Approved
Vault 1.6.2 3189 Monday, February 1, 2021 Approved
Vault 1.6.1 618 Thursday, January 21, 2021 Approved
Vault 1.5.5 3195 Friday, October 23, 2020 Approved
Vault 1.5.4 2428 Thursday, October 22, 2020 Approved
Vault 1.5.3 444 Thursday, October 22, 2020 Approved
Vault 1.5.2 2217 Wednesday, August 26, 2020 Approved
Vault 1.5.0 1540 Wednesday, July 22, 2020 Approved


### 21 April 2021


* The PKI Secrets Engine tidy functionality may cause Vault to exclude revoked-but-unexpired certificates from the
Vault CRL. This vulnerability affects Vault and Vault Enterprise 1.5.1 and newer and was fixed in versions
1.5.8, 1.6.4, and 1.7.1. (CVE-2021-27668)
* The Cassandra Database and Storage backends were not correctly verifying TLS certificates. This issue affects all
versions of Vault and Vault Enterprise and was fixed in versions 1.6.4, and 1.7.1. (CVE-2021-27400)


* go: Update to Go 1.15.11 GH-11395


* auth/jwt: Adds ability to directly provide service account JSON in G Suite provider config. GH-11388
* core: Add tls_max_version listener config option. GH-11226
* core: Add metrics for standby node forwarding. GH-11366
* core: allow arbitrary length stack traces upon receiving SIGUSR2 (was 32MB) GH-11364


* core: Fix cleanup of storage entries from cubbyholes within namespaces. GH-11408
* core: Fix goroutine leak when updating rate limit quota GH-11371
* core: Fix storage entry leak when revoking leases created with non-orphan batch tokens.[GH-11377
* core: requests forwarded by standby weren't always timed out. GH-11322
* pki: Only remove revoked entry for certificates during tidy if they are past their NotAfter value GH-11367
* replication: Fix: mounts created within a namespace that was part of an Allow
filtering rule would not appear on performance secondary if created after rule
was defined. GH-1807
* replication: Perf standby nodes on newly enabled DR secondary sometimes couldn't connect to active node with TLS errors. GH-1823
* secrets/database/cassandra: Fixed issue where hostnames were not being validated when using TLS GH-11365
* secrets/database/cassandra: Updated default statement for password rotation to allow for special characters. This applies to root and static credentials. GH-11262
* storage/dynamodb: Handle throttled batch write requests by retrying, without which writes could be lost. GH-10181
* storage/raft: leader_tls_servername wasn't used unless leader_ca_cert_file and/or mTLS were configured. GH-11252
* ui: Add root rotation statements support to appropriate database secret engine plugins GH-11404
* ui: Fix bug where the UI does not recognize version 2 KV until refresh, and fix [object Object] error message GH-11258
* ui: Fix footer URL linking to the correct version changelog. GH-11283
* ui: Fix namespace-bug on login GH-11182
* ui: Fix status menu no showing on login GH-11213
* ui: fix issue where select-one option was not showing in secrets database role creation GH-11294

## Previous Releases
For more information on previous releases, check out the changelog on GitHub.

This package has no dependencies.

Discussion for the Vault Package

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.
comments powered by Disqus