From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pdm-devel@lists.proxmox.com, Shannon Sterz <s.sterz@proxmox.com>
Cc: yew-devel@lists.proxmox.com
Subject: [yew-devel] applied: [pdm-devel] [PATCH yew-comp 2/2] token_panel: implement a token panel
Date: Sat, 27 Sep 2025 18:57:42 +0200 [thread overview]
Message-ID: <175899225402.828811.7169176055208637375.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250924145137.407070-6-s.sterz@proxmox.com>
On Wed, 24 Sep 2025 16:51:34 +0200, Shannon Sterz wrote:
> this is analogous to the user panel. the token panel allows adding,
> editing and remove api tokens. existing tokens can also be
> re-generated and their permissions can be displayed.
>
>
Applied, thanks! With a bunch of follow-ups.
Left open for now is the (probably) not required duplicate of the secret value
field into another hidden one, moving the note into the InputPanel to ensure
alignment matches and also adding a small per-field copy button, replacing the
current single one that just takes care of the secret value.
Oh, and it might also be sensible to change the secret field into a password
like one, i.e. hiding the value per default, as better resistance against a
shoulder surfing (and snapping a foto) attack.
[2/2] token_panel: implement a token panel
commit: b3ec5e54d8949233379dd6a518b0ddf90226a88f
_______________________________________________
yew-devel mailing list
yew-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/yew-devel
prev parent reply other threads:[~2025-09-27 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250924145137.407070-1-s.sterz@proxmox.com>
[not found] ` <20250924145137.407070-5-s.sterz@proxmox.com>
2025-09-27 16:57 ` [yew-devel] applied: [pdm-devel] [PATCH yew-comp 1/2] utils/user_panel: factor out epoch_to_input_value helper Thomas Lamprecht
[not found] ` <20250924145137.407070-6-s.sterz@proxmox.com>
2025-09-27 16:57 ` 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=175899225402.828811.7169176055208637375.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pdm-devel@lists.proxmox.com \
--cc=s.sterz@proxmox.com \
--cc=yew-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