Skip to content

Commit 87974ef

Browse files
calvntomhjp
andauthored
Update website/content/docs/upgrading/upgrade-to-1.9.x.mdx
Co-authored-by: Tom Proctor <tomhjp@users.noreply.github.com>
1 parent 731508b commit 87974ef

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

website/content/docs/upgrading/upgrade-to-1.9.x.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -99,8 +99,8 @@ See [this blog post](https://go.dev/blog/tls-cipher-suites) for more information
9999
- Existing Vault installations that use the [Identity Token
100100
backend](/api-docs/secret/identity/tokens) and have [named
101101
keys](/api-docs/secret/identity/tokens#create-a-named-key) generated will
102-
encounter a panic when any of those existing keys are rotated once passed its
103-
`rotation_period`. This issue affects Vault 1.9.0, and fixed in Vault 1.9.1. The
102+
encounter a panic when any of those existing keys pass their
103+
`rotation_period`. This issue affects Vault 1.9.0, and is fixed in Vault 1.9.1. The
104104
workarounds for this issue are to either 1) delete any existing keys before the
105105
update, or 2) increase the rotation period to allow ample time for updating past
106106
1.9.0 before a rotation can occur. Workarounds are not necessary if an update to

0 commit comments

Comments
 (0)