Skip to content

Commit 0b9ed13

Browse files
[docs] add known issue where static roles get rotated on upgrade (#30145)
* add known issue where static roles get rotated on upgrade #VAULT-35117) * Update website/content/partials/known-issues/static-role-premature-rotations.mdx Co-authored-by: Sarah Chavis <[email protected]> * Update website/content/partials/known-issues/static-role-premature-rotations.mdx Co-authored-by: Sarah Chavis <[email protected]> --------- Co-authored-by: Sarah Chavis <[email protected]>
1 parent d17b626 commit 0b9ed13

File tree

9 files changed

+27
-3
lines changed

9 files changed

+27
-3
lines changed

website/content/docs/release-notes/1.16.1.mdx

+1-1
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ description: |-
3131
| New default (1.16.13) | [Vault product usage metrics reporting](/vault/docs/upgrading/upgrade-to-1.6.x#product-usage-reporting) |
3232
| Deprecation (1.16.13) | [`default_report_months` is deprecated for the `sys/internal/counters` API](/vault/docs/upgrading/upgrade-to-1.16.x#activity-log-changes) |
3333
| Known Issue (1.16.16) | [Authorization failures using Azure federated identity credentials](/vault/docs/upgrading/upgrade-to-1.16.x#authorization-failures-using-azure-federated-identity-credentials) |
34-
34+
| Known issue (1.16.16) | [Unexpected static role rotations on upgrade](/vault/docs/upgrading/upgrade-to-1.16.x#static-role-rotations)
3535

3636
## Vault companion updates
3737

website/content/docs/release-notes/1.17.0.mdx

+1
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,7 @@ description: |-
3131
| New default (1.17.9) | [Vault product usage metrics reporting](/vault/docs/upgrading/upgrade-to-1.17.x#product-usage-reporting) |
3232
| Deprecation (1.17.9) | [`default_report_months` is deprecated for the `sys/internal/counters` API](/vault/docs/upgrading/upgrade-to-1.17.x#activity-log-changes) |
3333
| Known Issue (1.17.12) | [Authorization failures using Azure federated identity credentials](/vault/docs/upgrading/upgrade-to-1.17.x#authorization-failures-using-azure-federated-identity-credentials) |
34+
| Known issue (1.17.12) | [Unexpected static role rotations on upgrade](/vault/docs/upgrading/upgrade-to-1.17.x#static-role-rotations)
3435

3536
## Vault companion updates
3637

website/content/docs/release-notes/1.18.0.mdx

+1
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,7 @@ description: |-
2020
| Beta feature removed (1.18) | [Request limiter removed](/vault/docs/upgrading/upgrade-to-1.18.x#request-limiter-configuration-removal) |
2121
| New default (1.18.2) | [Vault product usage metrics reporting](/vault/docs/upgrading/upgrade-to-1.18.x#product-usage-reporting) |
2222
| Known Issue (1.18.5) | [Authorization failures using Azure federated identity credentials](/vault/docs/upgrading/upgrade-to-1.18.x#authorization-failures-using-azure-federated-identity-credentials) |
23+
| Known issue (1.18.5) | [Unexpected static role rotations on upgrade](/vault/docs/upgrading/upgrade-to-1.18.x#static-role-rotations)
2324

2425
## Vault companion updates
2526

website/content/docs/release-notes/1.19.0.mdx

+2-1
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,8 @@ description: |-
2323
| Known issue (1.19.x, 1.18.x, 1.17.x, 1.16.x) | [Duplicate HSM keys creation when migrating to HSM from Shamir](/vault/docs/upgrading/upgrade-to-1.19.x#hsm-keys)
2424
| New behavior (1.19.0) | [Uppercase values are no longer forced to lower case](/vault/docs/upgrading/upgrade-to-1.19.x#case-sensitive)
2525
| Known issue (1.19.0) | [Login/token renewal failures after group changes](/vault/docs/upgrading/upgrade-to-1.19.x#group-writes)
26-
26+
| Known issue (1.19.0) | [Unexpected static role rotations on upgrade](/vault/docs/upgrading/upgrade-to-1.19.x#static-role-rotations)
27+
2728

2829
## Feature deprecations and EOL
2930

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

+2
Original file line numberDiff line numberDiff line change
@@ -240,3 +240,5 @@ more details, and information about opt-out.
240240
@include 'known-issues/database-skip-static-role-rotation.mdx'
241241

242242
@include 'known-issues/azure-unseal-regression.mdx'
243+
244+
@include 'known-issues/static-role-premature-rotations.mdx'

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

+2
Original file line numberDiff line numberDiff line change
@@ -211,3 +211,5 @@ more details, and information about opt-out.
211211
@include 'known-issues/database-skip-static-role-rotation.mdx'
212212

213213
@include 'known-issues/azure-unseal-regression.mdx'
214+
215+
@include 'known-issues/static-role-premature-rotations.mdx'

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

+2
Original file line numberDiff line numberDiff line change
@@ -146,3 +146,5 @@ more details, and information about opt-out.
146146
@include 'known-issues/database-skip-static-role-rotation.mdx'
147147

148148
@include 'known-issues/azure-unseal-regression.mdx'
149+
150+
@include 'known-issues/static-role-premature-rotations.mdx'

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

+3-1
Original file line numberDiff line numberDiff line change
@@ -97,4 +97,6 @@ As of Vault 1.19.0 the RADIUS authentication plugin will not force case sensitiv
9797

9898
@include 'known-issues/duplicate-hsm-key.mdx'
9999

100-
@include 'known-issues/1_19-failures-after-external-group-changes-standby.mdx'
100+
@include 'known-issues/1_19-failures-after-external-group-changes-standby.mdx'
101+
102+
@include 'known-issues/static-role-premature-rotations.mdx'
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
### Static role rotations on upgrade ((#static-role-rotations))
2+
3+
#### Affected Versions
4+
- 1.19.0, 1.18.5, 1.17.12, 1.16.16
5+
6+
#### Issue
7+
Vault automatically rotates existing static roles tied to database and LDAP
8+
credentials once when upgrading to an affected version. After the one-time
9+
rotation, the static roles behave as expected.
10+
11+
#### Workaround
12+
If you rely on LDAP or static database roles, avoid upgrading to the affected
13+
versions until we fix the issue.

0 commit comments

Comments
 (0)