Change Log

All notable changes to this project will be documented in this file. This change log follows the conventions of keepachangelog.com.

Unreleased

...

2.0.559-rc1 - 2023-09-08

This is a major release which completely rewrites the library code. New releases will be under the com.amperity/vault-clj coordinate. See the Upgrading from 1.x document for details on the changes.

1.1.3 - 2022-05-31

Changed

• Updated dependency versions.

1.1.2 - 2022-02-01

Fixed

• Correctly interpret the :wrap-info payload when creating tokens with a wrapper.

1.1.1 - 2022-01-31

Fixed

• All write commands are sent with the correct JSON body encoding, instead of accidentally encoding them as a form-params string. #62

1.1.0 - 2022-01-28

Changed

• Updated dependency versions.

Added

• Added create-orphan-token! method to support the /auth/token/create-orphan endpoint. #61

1.0.6 - 2021-08-25

Changed

• Added github authentication implementation. #58
• Minor fix for broken authenticate request handling

1.0.5 - 2021-08-19

Changed

• Added integration tests to avoid stale mock test details, cover end-to-end. #57
• Fixed broken functionality in 1.0.4 mainly around json parsing. #55

1.0.4 - 2021-07-19

Changed

• Update dep clj-http to http-kit, add babashka support #54

1.0.3 - 2021-04-26

Changed

• Fix authenticate logging for syntax replacement #51

1.0.2 - 2021-03-31

Changed

• Add aws-iam authentication support #50

1.0.1 - 2021-01-04

Changed

• Updated various dependencies. #48
• Migrate to cljstyle and clj-kondo for style and linting.

1.0.0 - 2019-12-13

THIS RELEASE CONTAINS SOME BREAKING CHANGES!

Changed

• Large internal refactor that may result in unexpected behavior #35

Added

• Added support for externally defined secret engines #33
• Added support for the KV V2 API #39

Fixed

• Bugfix for mocking delete #35

0.7.1 - 2019-11-20

Added

• Added support for auth mount points to support authentication methods under a custom mount point #27

Fixed

• Bugfix in mock client so that it acts more similarly to http client when creating tokens (create-token!) #36

0.7.0 - 2019-06-20

Changed

• Upgrade Clojure to 1.10.0.
• Upgrade clj-http to 3.7.0.
• Drop dependency on digest library.
• Other minor dependency updates.

0.6.6 - 2019-06-14

Changed

• Open authentication (type) dispatch to multimethod #28

0.6.5 - 2018-11-5

Changed

• Fix client token lease renewal a034b3

0.6.4 - 2018-10-29

Changed

• Fix client token lease renewal even when no secret leases ca731d

0.6.3 - 2018-10-16

Added

• Support Wrap Token authentication. #25

Changed

• Fix client token renewal code path to update internal state. #26
• Use digest instead of transitive apache lib for hashing. 362f1ab

0.6.2 - 2018-08-09

Added

• Wrap-token authentication mechanism.
• Environment configuration for wrapped tokens via VAULT_WRAP_TOKEN.
• AppRole client configuration via VAULT_ROLE_ID and VAULT_SECRET_ID.

Changed

• Upgrade Clojure to 1.9
• Hash role-id when logging app-role authentication status.

0.6.0 - 2018-04-23

Added

• Support AppRole authentication method. #21
• Support Kubernetes JWT authentication method. #24
• The read-secret method supports a :force-read flag which will ignore valid leases and always re-read the path. #22

Changed

• Upgrade to CircleCI 2.0. #23
• The read-secret method now returns the response body on 200 status codes to plumb through important information. 204 writes still return true. #17 #18

0.5.1 - 2017-09-26

Added

• HTTP client supports LDAP authentication using the :ldap type. #14 #16

0.5.0 - 2017-07-07

Added

• API errors thrown by the HTTP client have :type :vault.client.http/api-error in their ex-data.
• The HTTP client supports an additional :http-opts property which will be merged into the clj-http requests to the Vault server. This provides a way to set custom timeouts, TLS settings, and more. #10
• The read-secret method supports a :not-found option which will be returned if set and a secret path is not present. Otherwise, clients consistently throw exceptions. #7

0.4.1 - 2017-05-10

Added

• The HTTP Vault client component accepts a :revoke-on-stop? option to control the outstanding lease revocation.

Changed

• Outstanding leases are no longer revoked on client stop by default.
• The default lease check period and renewal window changed to one and five minutes, respectively. This allows for better lease utilization, as the previous twenty minute window was too large for short-lived leases.

0.4.0 - 2017-01-06

THIS RELEASE CONTAINS BREAKING CHANGES!

Most of the code in the library has been refactored and rewritten with the goal of providing a more fully-featured client for the Vault API. The HTTP client is now a proper system component which manages a background thread to track, renew, and rotate leased secrets. This enables the usage of dynamic secret backends like AWS, PostgreSQL, and more!

Additionally, the mock client implementation has been enhanced to implement most of the API methods and provides a URL-based constructor to load mock secret data in at runtime. This makes testing code without a Vault instance much simpler.

Added

• Added amperity/envoy to define the environment variables used by the environment-based client constructor.
• The HTTPClient record implements the Lifecycle protocol from the component library to manage an internal lease maintenance thread.
• Added the vault.core/new-client multimethod which constructs a client based on the given URI scheme. This makes environment-driven construction simpler.
• Added the vault.env/config-client constructor which builds a client based on the VAULT_ADDR config and authenticates it based on the available credentials. Currently supports VAULT_TOKEN and VAULT_APP_ID/VAULT_USER_ID.
• The vault client revokes outstanding leases when stopped.

Changed

• vault.cache namespace renamed to vault.lease, significant functionality added for dealing with lease information.
• vault.client namespace renamed to vault.core, with the single Client protocol split into a number of more focused protocols.
• Client implementations moved into dedicated namespaces vault.client.mock and vault.client.http.
• Downgraded clj-http to the stable 2.3.0 version to simplify dependency management.
• Deprecated the vault.env/init-app-client constructor.

0.3.4 - 2016-11-16

Added

• Add create-token! API support in the Client protocol. Tokens can be returned as wrapped responses.
• Add unwrap! API support in the Client protocol.

0.3.3 - 2016-11-04

Changed

• vault.env/init-app-client uses VAULT_ADDR as the primary configuration variable, falling back to VAULT_URL for compatibility.

Fixed

• HTTP 307 redirects from clustered Vault instances will be followed up to two times in order to connect to the correct master node.

0.3.2 - 2016-10-26

Added

• Add delete-secret! API support in the Client protocol.
• memory-client returns a mock in-memory client implementation for testing.
• Numerous unit tests to cover environment and caching logic.

0.3.1 - 2016-10-25

Added

• The normal HTTP client supports internal lease caching directly via the vault.cache namespace.

Fixed

• Tokens used for direct authentication are trimmed as a precation to prevent odd header-based HTTP errors.

0.3.0 - 2016-10-18

With this version, the project has been forked to the Amperity organization.

Added

• authenticate! now supports the userpass auth backend.
• Add write support in the client via the write-secret! protocol method.
• Environment configuration resolution via the vault.env/load! function. This takes a map of env vars with some potential secret values as Vault paths. Listed variables of the form vault:<path> are resolved as secret values.

0.2.0 - 2016-03-25

Changed

• authenticate! takes an auth-type keyword and a map of credentials now instead of only supporting the :app-id auth type.

Added

• Added direct token authentication with type :token and credentials of the token string.
• Added support for listing secrets with the client protocol.

0.1.0 - 2015-10-27

Added

• Initial library implementation.