Skip to content

Commit 383c9c5

Browse files
committed
add 1.20.x updates
1 parent 1c6d81e commit 383c9c5

File tree

3 files changed

+14
-3
lines changed

3 files changed

+14
-3
lines changed

content/vault/global/partials/important-changes/summary-tables/1_20.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Introduced | Recommendations | Edition | Change
1616
1.20.0 | **Yes** | All | [Key pair authentication for Snowflake DB secrets engine](/vault/docs/v1.20.x/updates/important-changes#snowflake-keypair-auth)
1717
1.20.0 | **Yes** | All | [Audience warning for Kubernetes authentication roles](#k8-audience-warning)
1818
1.20.3 | No | All | [JSON Payload Limits](/vault/docs/v1.20.x/updates/important-changes#json-limits)
19-
19+
1.20.5 | **Yes** | All | [Rotation manager schedule strings in UTC](/vault/docs/v1.20.x/updates/important-changes#rotation-manager-utc)
2020

2121

2222
### Known issues

content/vault/v1.20.x/content/docs/updates/important-changes.mdx

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -231,6 +231,17 @@ You would then authenticate with the command below.
231231
$ vault write auth/kubernetes/login role=demo audience="my_audience" jwt=...
232232
```
233233

234+
235+
### Rotation manager schedue strings in UTC ((#rotation-manager-utc))
236+
237+
| Change | Affected version | Vault edition
238+
| ------------ | ---------------- | -------------
239+
| New behavior | 1.20.5+ | Enterprise
240+
241+
Vault interprets `rotation_schedule` strings relative to UTC to match the
242+
behavior of static role rotations in the database plugin. Old rotations use
243+
their existing schedule until you manually update rotation with an API call.
244+
234245
---
235246

236247

content/vault/v1.20.x/content/partials/rotationfields.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,8 @@
88
defining the schedule on which Vault should rotate the root token. Standard
99
cron-style time format uses five fields to define the minute, hour, day of
1010
month, month, and day of week respectively. For example, `0 0 * * SAT` tells
11-
Vault to rotate the root token every Saturday at 00:00. **You must set one of
12-
`rotation_schedule` or `rotation_period`, but cannot set both**.
11+
Vault to rotate the root token every Saturday at 00:00. Vault interprets the schedule in UTC.
12+
**You must set one of `rotation_schedule` or `rotation_period`, but cannot set both**.
1313
- `rotation_window` `(string/integer: 0)` – <EnterpriseAlert product="vault" inline />
1414
The maximum amount of time, in seconds, allowed to complete
1515
a rotation when a scheduled token rotation occurs. If Vault cannot rotate the

0 commit comments

Comments
 (0)