From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
	by lore.proxmox.com (Postfix) with ESMTPS id 0435A1FF13B
	for <inbox@lore.proxmox.com>; Wed, 06 May 2026 02:09:39 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id E19B910D1D;
	Wed,  6 May 2026 02:09:36 +0200 (CEST)
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com,
	Hannes Laimer <h.laimer@proxmox.com>
Subject: applied: [PATCH access-control/manager 0/2] fixes #7504: add support
 for regenerating secrets
Date: Wed,  6 May 2026 02:08:11 +0200
Message-ID: <177802597091.2857170.3623066406103327485.b4-ty@b4>
X-Mailer: git-send-email 2.47.3
In-Reply-To: <20260417123504.143556-1-h.laimer@proxmox.com>
References: <20260417123504.143556-1-h.laimer@proxmox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2
X-Bm-Transport-Timestamp: 1778026035805
X-SPAM-LEVEL: Spam detection results:  0
	AWL                     0.003 Adjusted score from AWL reputation of From:
 address
	BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
	DMARC_MISSING             0.1 Missing DMARC policy
	KAM_DMARC_STATUS         0.01 Test Rule for DKIM or SPF Failure with Strict
 Alignment
	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: 2LF5BEYQ5EO4EFKYMFI7HAMEKJEUOWXV
X-Message-ID-Hash: 2LF5BEYQ5EO4EFKYMFI7HAMEKJEUOWXV
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 <pve-devel.lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Owner: <mailto:pve-devel-owner@lists.proxmox.com>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Subscribe: <mailto:pve-devel-join@lists.proxmox.com>
List-Unsubscribe: <mailto:pve-devel-leave@lists.proxmox.com>

On Fri, 17 Apr 2026 14:35:02 +0200, Hannes Laimer wrote:
> Allows rotating secrets without having to re-create the whole token.
> Like already possible in pbs.
> 
> pve-access-control:
> 
> Hannes Laimer (1):
>   api: token: support regenerating the secret on update
> 
> [...]

Applied, thanks!

[1/1] api: token: support regenerating the secret on update
      commit: ea5d51c56fb0a87591f6a338f432e3e689a1e8a9

[1/1] ui: token: add regenerate secret button
      commit: b0381cdac8f9af1324b725f4f3d5daff53f683ab