This page contains the list of deprecations and important or breaking changes for Vault 0.6.2. Please read it carefully.
In 0.6.1 this feature was in beta and required opting-in, but is now enabled by
default. This can be disabled via the
"disable_clustering" parameter in
Vault's config, or
per-request with the
Creating or updating a role now requires at least one constraint to be enabled,
whereas previously it was sufficient to require only the role ID by itself.
Currently there are two constraints:
bind_secret_id is enabled by default. Roles which were previously using only
the role ID for authentication will continue to work but will require a
constraint to be specified if updated.
New keys in
transit using convergent mode will use a new nonce derivation
mechanism rather than require the user to supply a nonce. While not explicitly
increasing security, it minimizes the likelihood that a user will use the mode
improperly and impact the security of their keys. Keys in convergent mode that
were created in 0.6.1 will continue to work with the same mechanism
Following in the footsteps of
etcd storage backend now
ha_enabled be explicitly specified in the configuration file.
The backend currently has known broken HA behavior, so this flag discourages
use by default without explicitly enabling it. If you are using this
functionality, when upgrading, you should set
starting the new versions of Vault.
sys/wrapping/unwrap endpoint should be used instead as it provides
additional security, auditing, and other benefits. The ability to read directly
will be removed in a future release.
In previous versions of Vault the default was 30 days, but changing it to 32 days allows some operations (e.g. reauthenticating, renewing, etc.) to be performed via a monthly cron job.
Secret ID and Secret ID accessors are no longer part of request URLs. The
DELETE operations are now moved to new endpoints (
/destroy) which consumes the input from the body via
not the URL.
In prior versions a bug caused the
bound_iam_role_arn value in the
auth method to actually use the instance profile ARN. This has been
corrected, but as a result there is a behavior change. To match using the
instance profile ARN, a new parameter
bound_iam_instance_profile_arn has been
added. Existing roles will automatically transfer the value over to the correct
parameter, but the next time the role is updated, the new meanings will take