From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 013961FF09D for ; Sun, 15 Nov 2026 20:41:37 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 054F8216DC; Sun, 15 Nov 2026 20:41:03 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com Subject: [PATCH v2 docs 9/19] user management: document extending tokens on secret regeneration Date: Sun, 15 Nov 2026 20:40:30 +0100 Message-ID: <20261115194043.3947825-10-t.lamprecht@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261115194043.3947825-1-t.lamprecht@proxmox.com> References: <20261115194043.3947825-1-t.lamprecht@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794771649599 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.230 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: Z7PTKQVTO3DRT7IHJ72TZON7LFL6ODQR X-Message-ID-Hash: Z7PTKQVTO3DRT7IHJ72TZON7LFL6ODQR X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Describe the new allow-extension-on-regenerate policy setting and how to rotate a token in place with it, in the web interface and on the command line. Signed-off-by: Thomas Lamprecht --- new in v2 pveum.adoc | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/pveum.adoc b/pveum.adoc index 7e043d9..a5887d4 100644 --- a/pveum.adoc +++ b/pveum.adoc @@ -154,6 +154,22 @@ keep working. A new expiration date must be within the limit. With only be shortened, or set if it has none. Tokens can always be deleted and recreated. +With `allow-extension-on-regenerate`, an existing token can still be +extended within the limit when its secret is regenerated in the same +request. The old secret stops working, like it would when recreating the +token, so tools can rotate their tokens in place without setting up the +permissions again. In the web interface, enable *Regenerate Secret* in the +token edit dialog and set the new expiration date. On the command line, pass +the new expiration date in Unix epoch seconds: + +[source,bash] +---- +pveum user token modify --expire --regenerate 1 +---- + +Like on creation, the new secret is only displayed once, so update the tool +to use it right away. + NOTE: The policy also applies to tokens that other tools create through the API, for example when adding the cluster as a remote to Proxmox Datacenter Manager. For tools that do not set an expiration date, set -- 2.47.3