Downloads of v 1.1.0:


Last Update:

19 Mar 2019

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp


vault hashicorp


This is not the latest version of Vault available.

1.1.0 | Updated: 19 Mar 2019



Downloads of v 1.1.0:



Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Vault 1.1.0

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

See docs at

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

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

See docs at

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

Requires Otter Chocolatey Extension. See docs at

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

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install vault version="1.1.0" 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 by moderator Pauby on 27 Mar 2019.


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 = '895252424cbdc23ed524f63741fd472a7a04fe508a58dead76d9f6422b465729'
$checksum64 = 'b26de17832cb3a49d49017f5a3509e53d83547c275c85f81e045e58670b4061c'
$version = '1.1.0'
$url = "$($version)/vault_$($version)"
$url64bit = "$($version)/vault_$($version)"

$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 613 Thursday, January 21, 2021 Approved
Vault 1.5.5 3174 Friday, October 23, 2020 Approved
Vault 1.5.4 1465 Thursday, October 22, 2020 Approved
Vault 1.5.3 176 Thursday, October 22, 2020 Approved
Vault 1.5.2 2209 Wednesday, August 26, 2020 Approved
Vault 1.5.0 1489 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 1267 Thursday, April 9, 2020 Approved

1.1.0 (March 18th, 2019)


  • auth/jwt: The groups_claim_delimiter_pattern field has been removed. If the
    groups claim is not at the top level, it can now be specified as a
  • auth/jwt: Roles now have a "role type" parameter with a default type of
    "oidc". To configure new JWT roles, a role type of "jwt" must be explicitly
  • cli: CLI commands deprecated in 0.9.2 are now removed. Please see the CLI
    help/warning output in previous versions of Vault for updated commands.
  • core: Vault no longer automatically mounts a K/V backend at the "secret/"
    path when initializing Vault
  • core: Vault's cluster port will now be open at all times on HA standby nodes
  • plugins: Vault no longer supports running netRPC plugins. These were
    deprecated in favor of gRPC based plugins and any plugin built since 0.9.4
    defaults to gRPC. Older plugins may need to be recompiled against the latest
    Vault dependencies.


  • Vault Agent Caching: Vault Agent can now be configured to act as a
    caching proxy to Vault. Clients can send requests to Vault Agent and the
    request will be proxied to the Vault server and cached locally in Agent.
    Currently Agent will cache generated leases and tokens and keep them
    renewed. The proxy can also use the Auto Auth feature so clients do not need
    to authenticate to Vault, but rather can make requests to Agent and have
    Agent fully manage token lifecycle.
  • OIDC Redirect Flow Support: The JWT auth backend now supports OIDC
    roles. These allow authentication via an OIDC-compliant provider via the
    user's browser. The login may be initiated from the Vault UI or through
    the vault login command.
  • ACL Path Wildcard: ACL paths can now use the + character to enable
    wild card matching for a single directory in the path definition.
  • Transit Auto Unseal: Vault can now be configured to use the Transit
    Secret Engine in another Vault cluster as an auto unseal provider.


  • auth/jwt: A default role can be set. It will be used during JWT/OIDC logins if
    a role is not specified.
  • auth/jwt: Arbitrary claims data can now be copied into token and alias metadata.
  • auth/jwt: An arbitrary set of bound claims can now be configured for a role.
  • auth/jwt: The name "oidc" has been added as an alias for the jwt backend. Either
    name may be specified in the auth enable command.
  • command/server: A warning will be printed when 'tls_cipher_suites' includes a
    blacklisted cipher suite or all cipher suites are blacklisted by the HTTP/2
    specification [GH-6300]
  • core/metrics: Prometheus pull support using a new sys/metrics endpoint. [GH-5308]
  • core: On non-windows platforms a SIGUSR2 will make the server log a dump of
    all running goroutines' stack traces for debugging purposes [GH-6240]
  • replication: The inital replication indexing process on newly initialized or upgraded
    clusters now runs asynchronously
  • sentinel: Add token namespace id and path, available in rules as and token.namespace.path
  • ui: The UI is now leveraging OpenAPI definitions to pull in fields for various forms.
    This means, it will not be necessary to add fields on the go and JS sides in the future.


  • auth/jwt: Apply bound_claims validation across all login paths
  • auth/jwt: Update bound_audiences validation during non-OIDC logins to accept
    any matched audience, as documented and handled in OIDC logins [JWT-30]
  • auth/token: Fix issue where empty values for token role update call were
    ignored [GH-6314]
  • core: The operator migrate command will no longer hang on empty key names
  • identity: Fix a panic at login when external group has a nil alias [GH-6230]
  • namespaces: Clear out identity store items upon namespace deletion
  • replication/perfstandby: Fixed a bug causing performance standbys to wait
    longer than necessary after forwarding a write to the active node
  • replication/mountfilter: Fix a deadlock that could occur when mount filters
    were updated [GH-6426]
  • secret/kv: Fix issue where a v1→v2 upgrade could run on a performance
    standby when using a local mount
  • secret/ssh: Fix for a bug where attempting to delete the last ssh role
    in the zeroaddress configuration could fail [GH-6390]
  • secret/totp: Uppercase provided keys so they don't fail base32 validation
  • secret/transit: Multiple HMAC, Sign or Verify operations can now be
    performed with one API call using the new batch_input parameter [GH-5875]
  • sys: sys/internal/ui/mounts will no longer return secret or auth mounts
    that have been filtered. Similarly, sys/internal/ui/mount/:path will
    return a error response if a filtered mount path is requested. [GH-6412]
  • ui: Fix for a bug where you couldn't access the data tab after clicking on
    wrap details on the unwrap page [GH-6404]
  • ui: Fix an issue where the policies tab was erroneously hidden [GH-6301]
  • ui: Fix encoding issues with kv interfaces [GH-6294]

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