2019-04-12 00:34:40 +00:00
|
|
|
---
|
2020-01-18 00:18:09 +00:00
|
|
|
layout: docs
|
|
|
|
|
page_title: Upgrading to Vault 1.1.1 - Guides
|
2019-04-12 00:34:40 +00:00
|
|
|
description: |-
|
|
|
|
|
This page contains the list of deprecations and important or breaking changes
|
|
|
|
|
for Vault 1.1.1. Please read it carefully.
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# Overview
|
|
|
|
|
|
|
|
|
|
This page contains the list of deprecations and important or breaking changes
|
|
|
|
|
for Vault 1.1.0 compared to 1.1.1. Please read it carefully.
|
|
|
|
|
|
2023-07-18 21:07:55 +00:00
|
|
|
## Known issues
|
2019-04-16 17:53:06 +00:00
|
|
|
|
2019-07-30 16:37:45 +00:00
|
|
|
### Issue with some KVv2 mounts
|
|
|
|
|
|
2019-04-16 17:53:06 +00:00
|
|
|
There is a known issue that could cause the upgrade to 1.1.1 to fail under
|
|
|
|
|
certain circumstances. This issue occurs when a KV version 2 mount exists but
|
2019-10-15 19:58:03 +00:00
|
|
|
contains no data. This will be fixed in 1.1.2. Additionally a work around does
|
2019-04-16 17:53:06 +00:00
|
|
|
exist: prior to upgrading ensure all KV v2 mounts have at least one key written
|
2019-10-15 19:58:03 +00:00
|
|
|
to it.
|
2019-04-16 17:53:06 +00:00
|
|
|
|
2023-07-18 21:07:55 +00:00
|
|
|
### Change in LDAP group CN handling
|
2019-07-30 16:37:45 +00:00
|
|
|
|
|
|
|
|
A bug fix to allow group CNs to be found from an LDAP server in lowercase `cn`
|
|
|
|
|
as well as uppercase `CN` had an unintended consequence. If prior to that a
|
|
|
|
|
group used `cn`, as in `cn=foo,ou=bar` then the group that would need to be put
|
|
|
|
|
into place in the LDAP plugin to match against policies is `cn=foo,ou=bar`
|
|
|
|
|
since the CN would not be correctly found. After the change, the CN was
|
|
|
|
|
correctly found, but this would result in the group name being parsed as `foo`
|
|
|
|
|
and would not match groups using the full DN. In 1.1.5+, there is a boolean
|
|
|
|
|
config setting `use_pre111_group_cn_behavior` to allow reverting to the old
|
|
|
|
|
matching behavior; we also attempt to upgrade exiting configs to have that
|
|
|
|
|
defaulted to true.
|
|
|
|
|
|
2019-10-15 19:58:03 +00:00
|
|
|
### Long WAL replay
|
|
|
|
|
|
|
|
|
|
-> **NOTE:** This is a known issue applicable to _Vault Enterprise_.
|
|
|
|
|
|
|
|
|
|
During upgrades to 1.1.0, 1.1.1 or 1.1.2, Vault replication secondaries may
|
|
|
|
|
require an automatically-triggered reindex, either if upgrading from a pre-0.8
|
|
|
|
|
version of Vault or if a previously-issued reindex operation has failed in the
|
|
|
|
|
past. In these reindex scenarios, the secondary cluster will perform a complete
|
|
|
|
|
WAL replay, which can take a long time and is a partially blocking operation.
|
|
|
|
|
|
|
|
|
|
This is fixed in [Vault
|
2021-08-09 16:57:19 +00:00
|
|
|
1.1.3](https://github.com/hashicorp/vault/blob/main/CHANGELOG.md#113-june-5th-2019),
|
2019-10-15 19:58:03 +00:00
|
|
|
and we recommend upgrading to Vault 1.1.3+ rather than any prior 1.1.x version.
|
|
|
|
|
We also strongly recommend upgrading your Vault cluster to 1.1.3 if you are
|
|
|
|
|
running Vault Enterprise 1.1.0, 1.1.1 or 1.1.2.
|
|
|
|
|
|
2023-07-18 21:07:55 +00:00
|
|
|
## JWT/OIDC plugin
|
2019-04-12 00:34:40 +00:00
|
|
|
|
2019-10-15 19:58:03 +00:00
|
|
|
Logins of role_type "oidc" via the /login path are no longer allowed.
|
2019-04-12 00:34:40 +00:00
|
|
|
|
2023-07-18 21:07:55 +00:00
|
|
|
## ACL wildcards
|
2019-04-12 00:34:40 +00:00
|
|
|
|
|
|
|
|
New ordering defines which policy wins when there are multiple inexact matches
|
|
|
|
|
and at least one path contains `+`. `+*` is now illegal in policy paths. The
|
|
|
|
|
previous behavior simply selected any matching segment-wildcard path that
|
|
|
|
|
matched.
|
|
|
|
|
|
|
|
|
|
## Replication
|
|
|
|
|
|
|
|
|
|
Due to technical limitations, mounting and unmounting was not previously
|
|
|
|
|
possible from a performance secondary. These have been resolved, and these
|
|
|
|
|
operations may now be run from a performance secondary.
|
