From: Fiona Ebner <f.ebner@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: [pve-devel] superseded: [PATCH manager 2/5] user: password edit: clarify that password changes for PAM realm only apply to local node
Date: Mon, 7 Apr 2025 10:18:11 +0200 [thread overview]
Message-ID: <e2ae45b6-0629-4d40-b642-54ea39df1286@proxmox.com> (raw)
In-Reply-To: <66547236-ef82-4500-a1a7-153226d03cba@proxmox.com>
Am 06.04.25 um 20:01 schrieb Thomas Lamprecht:
> Am 04.12.24 um 12:37 schrieb Fiona Ebner:
>> Reported in the community forum:
>> https://forum.proxmox.com/threads/158518/
>>
>> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
>> ---
>> www/manager6/dc/UserView.js | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/www/manager6/dc/UserView.js b/www/manager6/dc/UserView.js
>> index 82bd2ee7..d5844674 100644
>> --- a/www/manager6/dc/UserView.js
>> +++ b/www/manager6/dc/UserView.js
>> @@ -68,10 +68,16 @@ Ext.define('PVE.dc.UserView', {
>> return false;
>> },
>> handler: function(btn, event, rec) {
>> + let hintHtml;
>> + if (rec.data['realm-type'] === 'pam') {
>> + hintHtml = gettext("For the PAM realm, this only applies to the local node.");
>
> I'd switch the place of `only` and `applies` and maybe s/local/connected/,
> like:
>
> For the PAM realm, this applies only to the connected node.
>
>> + }
>> +
>> Ext.create('Proxmox.window.PasswordEdit', {
>> userid: rec.data.userid,
>> confirmCurrentPassword: Proxmox.UserName !== 'root@pam',
>> autoShow: true,
>> + hintHtml: hintHtml,
>
> FYI, if variable name and property name match, i.e., left part of the colon is
> the same as the right part, you can just use that directly, e.g. `{ hintHtml }`
> is the same as `{ hintHtml: hintHtml }`; but not something that needs to be
> used as of now, but would be fine to be used.
>
>> minLength: 8,
>> listeners: {
>> destroy: () => reload(),
>
Sent a v2:
https://lore.proxmox.com/pve-devel/20250407081657.23658-1-f.ebner@proxmox.com/
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-04-07 8:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 11:37 [pve-devel] [PATCH widget-toolkit/manager/access-control/docs 0/5] " Fiona Ebner
2024-12-04 11:37 ` [pve-devel] [PATCH widget-toolkit 1/5] password edit: support specifying a hint Fiona Ebner
2025-04-06 17:57 ` [pve-devel] applied: " Thomas Lamprecht
2024-12-04 11:37 ` [pve-devel] [PATCH manager 2/5] user: password edit: clarify that password changes for PAM realm only apply to local node Fiona Ebner
2025-04-06 18:01 ` Thomas Lamprecht
2025-04-07 8:18 ` Fiona Ebner [this message]
2024-12-04 11:37 ` [pve-devel] [PATCH access-control 3/5] api: " Fiona Ebner
2025-04-04 17:21 ` [pve-devel] applied: " Thomas Lamprecht
2024-12-04 11:37 ` [pve-devel] [PATCH access-control 4/5] api: password: use singular they pronoun Fiona Ebner
2025-04-04 17:21 ` [pve-devel] applied: " Thomas Lamprecht
2024-12-04 11:37 ` [pve-devel] [PATCH docs 5/5] user management: clarify that password changes for PAM realm only apply to local node Fiona Ebner
2025-04-06 17:56 ` [pve-devel] applied: " Thomas Lamprecht
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=e2ae45b6-0629-4d40-b642-54ea39df1286@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal