Skip to content

Commit

Permalink
docs: add known issues section to 1.9.x upgrade guide (#13662)
Browse files Browse the repository at this point in the history
* docs: add known issues section to 1.9.x upgrade guide

* minor rephrasing on oidc known issue

* use relative references for URLs

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

Co-authored-by: Tom Proctor <[email protected]>

* update known issues section for id token

Co-authored-by: Tom Proctor <[email protected]>
  • Loading branch information
calvn and tomhjp authored Jan 19, 2022
1 parent e2d713a commit 8056125
Showing 1 changed file with 15 additions and 0 deletions.
15 changes: 15 additions & 0 deletions website/content/docs/upgrading/upgrade-to-1.9.x.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -95,3 +95,18 @@ respects the order of suites given in `tls_cipher_suites`.

See [this blog post](https://go.dev/blog/tls-cipher-suites) for more information.

## Known Issues

### Identity Token Backend Key Rotations

Existing Vault installations that use the [Identity Token
backend](/api-docs/secret/identity/tokens) and have [named
keys](/api-docs/secret/identity/tokens#create-a-named-key) generated will
encounter a panic when any of those existing keys pass their
`rotation_period`. This issue affects Vault 1.9.0, and is fixed in Vault 1.9.1.
Users should upgrade directly to 1.9.1 or above in order to avoid this panic.

If a panic is encountered after an upgrade to Vault 1.9.0, the named key will be
corrupted on storage and become unusable. In this case, the key will need to be
deleted and re-created. A fix to fully mitigate this panic will be addressed on
Vault 1.9.3.

0 comments on commit 8056125

Please sign in to comment.