Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: add known issues section to 1.9.x upgrade guide #13662

Merged
merged 5 commits into from
Jan 19, 2022
Merged

docs: add known issues section to 1.9.x upgrade guide #13662

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
41a7ee6
docs: add known issues section to 1.9.x upgrade guide
calvn Jan 13, 2022
241089e
minor rephrasing on oidc known issue
calvn Jan 13, 2022
731508b
use relative references for URLs
calvn Jan 13, 2022
87974ef
Update website/content/docs/upgrading/upgrade-to-1.9.x.mdx
calvn Jan 18, 2022
458aaaa
update known issues section for id token
calvn Jan 19, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions website/content/docs/upgrading/upgrade-to-1.9.x.mdx
View file
Open in desktop
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.