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 [thread overview]
Message-ID: <177802597091.2857170.3623066406103327485.b4-ty@b4> (raw)
In-Reply-To: <20260417123504.143556-1-h.laimer@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
prev parent reply other threads:[~2026-05-06 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 12:35 [PATCH access-control/manager 0/2] fixes #7504: add support for regenerating secrets Hannes Laimer
2026-04-17 12:35 ` [PATCH pve-access-control 1/2] api: token: support regenerating the secret on update Hannes Laimer
2026-04-17 12:35 ` [PATCH pve-manager 2/2] ui: token: add regenerate secret button Hannes Laimer
2026-05-06 0:08 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177802597091.2857170.3623066406103327485.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=h.laimer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox