From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH-SERIES manager] ui: user edit: improve 'keys' field
Date: Fri, 9 Feb 2024 14:08:18 +0100 [thread overview]
Message-ID: <20240209130821.51461-1-f.ebner@proxmox.com> (raw)
Nowadays, TFA is configured in the respective window, so only legacy
values require some special treatment. The only real use case for
actual legacy keys is syncing them from LDAP. I wasn't sure if it
still makes sense to keep those editable, so the series is doing the
changes towards a more restricted field gradually.
Fiona Ebner (3):
ui: user edit: protect user's TFA settings again
ui: user edit: hide key field except for legacy values
ui: user edit: prohibit editing keys option
www/manager6/dc/UserEdit.js | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
--
2.39.2
next reply other threads:[~2024-02-09 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 13:08 Fiona Ebner [this message]
2024-02-09 13:08 ` [pve-devel] [PATCH manager 1/3] ui: user edit: protect user's TFA settings again Fiona Ebner
2024-04-23 14:52 ` [pve-devel] applied: " Thomas Lamprecht
2024-02-09 13:08 ` [pve-devel] [PATCH manager 2/3] ui: user edit: hide key field except for legacy values Fiona Ebner
2024-02-09 13:08 ` [pve-devel] [PATCH manager 3/3] ui: user edit: prohibit editing keys option Fiona Ebner
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=20240209130821.51461-1-f.ebner@proxmox.com \
--to=f.ebner@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