Downloads of v 0.7.1:


Last Update:

07 Jun 2017

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp


vault hashicorp


This is not the latest version of Vault available.

0.7.1 | Updated: 07 Jun 2017



Downloads of v 0.7.1:



Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Vault 0.7.1

This is not the latest version of Vault available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


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: 0.7.1
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

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

See docs at

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

Requires Otter Chocolatey Extension. See docs at

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

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install vault version="0.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.

This package was approved as a trusted package on 07 Jun 2017.


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.

$checksum = 'efdd4c064af9fe7ec5508ef07075a3c68192cd6a9ed3c68b201bbf9d5cd02112'
$checksum64 = '27f6f476650d61b1435bd8f24eca97ecabcb789e1e8a0f8388d59ac4f90517ad'
$url = ''
$url64bit = ''
$unzipLocation = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

Install-ChocolateyZipPackage -PackageName "vault" -Url "$url" -UnzipLocation "$unzipLocation" -Url64 "$url64bit" -ChecksumType 'sha256' -Checksum "$checksum" -Checksum64 "$checksum64"

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.6.1 614 Thursday, January 21, 2021 Approved
Vault 1.5.5 3174 Friday, October 23, 2020 Approved
Vault 1.5.4 1510 Thursday, October 22, 2020 Approved
Vault 1.5.3 180 Thursday, October 22, 2020 Approved
Vault 1.5.2 2210 Wednesday, August 26, 2020 Approved
Vault 1.5.0 1490 Wednesday, July 22, 2020 Approved
Vault 1.4.3 784 Friday, July 3, 2020 Approved
Vault 1.4.1 1627 Monday, May 4, 2020 Approved
Vault 1.4.0 1269 Thursday, April 9, 2020 Approved

0.7.1 (May 5th, 2017)


  • LDAP Auth Backend: Group membership queries will now run as the binddn user when binddn/bindpass are configured, rather than as the authenticating user as was the case previously.

  • AWS IAM Authentication: IAM principals can get Vault tokens automatically, opening AWS-based authentication to users, ECS containers, Lambda instances, and more. Signed client identity information retrieved using the AWS API sts:GetCallerIdentity is validated against the AWS STS service before issuing a Vault token. This backend is unified with the aws-ec2 authentication backend, and allows additional EC2-related restrictions to be applied during the IAM authentication; the previous EC2 behavior is also still available. [GH-2441]

  • MSSQL Physical Backend: You can now use Microsoft SQL Server as your Vault physical data store [GH-2546]

  • Lease Listing and Lookup: You can now introspect a lease to get its creation and expiration properties via sys/leases/lookup; with sudo capability you can also list leases for lookup, renewal, or revocation via that endpoint. Various lease functions (renew, revoke, revoke-prefix, revoke-force) have also been relocated to sys/leases/, but they also work at the old paths for compatibility. Reading (but not listing) leases via sys/leases/lookup is now a part of the current default policy. [GH-2650]

  • TOTP Secret Backend: You can now store multi-factor authentication keys in Vault and use the API to retrieve time-based one-time use passwords on demand. The backend can also be used to generate a new key and validate passwords generated by that key. [GH-2492]

  • Database Secret Backend & Secure Plugins (Beta): This new secret backend combines the functionality of the MySQL, PostgreSQL, MSSQL, and Cassandra backends. It also provides a plugin interface for extendability through custom databases. [GH-2200]


  • auth/cert: Support for constraints on subject Common Name and DNS/email Subject Alternate Names in certificates [GH-2595]
  • auth/ldap: Use the binding credentials to search group membership rather than the user credentials [GH-2534]
  • cli/revoke: Add -self option to allow revoking the currently active token [GH-2596]
  • core: Randomize x coordinate in Shamir shares [GH-2621]
  • tidy: Improvements to auth/token/tidy and sys/leases/tidy to handle more cleanup cases [GH-2452]
  • secret/pki: Add no_store option that allows certificates to be issued without being stored. This removes the ability to look up and/or add to a CRL but helps with scaling to very large numbers of certificates. [GH-2565]
  • secret/pki: If used with a role parameter, the sign-verbatim/<role> endpoint honors the values of generate_lease, no_store, ttl and max_ttl from the given role [GH-2593]
  • secret/pki: Add role parameter allow_glob_domains that enables defining names in allowed_domains containing * glob patterns [GH-2517]
  • secret/pki: Update certificate storage to not use characters that are not supported on some filesystems [GH-2575]
  • storage/etcd3: Add discovery_srv option to query for SRV records to find servers [GH-2521]
  • storage/s3: Support max_parallel option to limit concurrent outstanding requests [GH-2466]
  • storage/s3: Use pooled transport for http client [GH-2481]
  • storage/swift: Allow domain values for V3 authentication [GH-2554]


  • api: Respect a configured path in Vault's address [GH-2588]
  • auth/aws-ec2: New bounds added as criteria to allow role creation [GH-2600]
  • auth/ldap: Don't lowercase groups attached to users [GH-2613]
  • cli: Don't panic if vault write is used with the force flag but no path [GH-2674]
  • core: Help operations should request forward since standbys may not have appropriate info [GH-2677]
  • secret/mssql: Update mssql driver to support queries with colons [GH-2610]
  • secret/pki: Don't lowercase O/OU values in certs [GH-2555]
  • secret/pki: Don't attempt to validate IP SANs if none are provided [GH-2574]
  • secret/ssh: Don't automatically lowercase principles in issued SSH certs [GH-2591]
  • storage/consul: Properly handle state events rather than timing out [GH-2548]
  • storage/etcd3: Ensure locks are released if client is improperly shut down [GH-2526]

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