From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH manager 4/9] ui: token edit: only submit the expiration date when changed
Date: Wed, 23 Sep 2026 22:59:53 +0200 [thread overview]
Message-ID: <20260923210000.4031318-5-t.lamprecht@proxmox.com> (raw)
In-Reply-To: <20260923210000.4031318-1-t.lamprecht@proxmox.com>
The day-granular date field resubmits the stored expiration date
truncated to the start of its day, so any unrelated edit, for example
of the comment, silently shortened the stored date by up to a day.
Drop the value from the submission if the selected day was not
actually changed.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
---
www/manager6/dc/TokenEdit.js | 29 +++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
diff --git a/www/manager6/dc/TokenEdit.js b/www/manager6/dc/TokenEdit.js
index fc9f0cc2c..2baeb5b74 100644
--- a/www/manager6/dc/TokenEdit.js
+++ b/www/manager6/dc/TokenEdit.js
@@ -25,6 +25,21 @@ Ext.define('PVE.dc.TokenEdit', {
delete values.userid;
delete values.tokenid;
+ // the day-granular date field resubmits the expiration date truncated to the
+ // start of its day, drop it if the selected day was not actually changed to
+ // avoid silently shortening the stored date on unrelated edits
+ if (!win.isCreate && win.originalExpire !== undefined) {
+ let sameDay = 0;
+ if (win.originalExpire) {
+ let day = new Date(win.originalExpire * 1000);
+ day.setHours(0, 0, 0, 0);
+ sameDay = Math.floor(day.getTime() / 1000);
+ }
+ if (Number(values.expire) === sameDay) {
+ delete values.expire;
+ }
+ }
+
win.url += `${uid}/token/${tid}`;
return values;
},
@@ -91,6 +106,20 @@ Ext.define('PVE.dc.TokenEdit', {
});
}
},
+
+ setValues: function (values) {
+ let me = this;
+ // remember the stored expiration date to detect a real change on submission; the
+ // token grid's record carries it as a Date object, the API as epoch seconds
+ if (!me.isCreate && values.expire !== undefined) {
+ me.originalExpire =
+ values.expire instanceof Date
+ ? Math.floor(values.expire.getTime() / 1000)
+ : Number(values.expire);
+ }
+ me.callParent([values]);
+ },
+
apiCallDone: function (success, response, options) {
let res = response.result.data;
if (!success || !res.value) {
--
2.47.3
next prev parent reply other threads:[~2026-09-23 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 20:59 [PATCH cluster/access-control/manager/docs/proxmox 0/9] fix #7805: add a datacenter-wide API token policy Thomas Lamprecht
2026-09-23 20:59 ` [PATCH cluster 1/9] datacenter config: add token-policy option Thomas Lamprecht
2026-09-23 20:59 ` [PATCH access-control 2/9] fix #7805: api: token: enforce datacenter token policy Thomas Lamprecht
2026-09-23 20:59 ` [PATCH docs 3/9] user management: document the API " Thomas Lamprecht
2026-09-23 20:59 ` Thomas Lamprecht [this message]
2026-09-23 20:59 ` [PATCH manager 5/9] api: cluster options: return token-policy without Sys.Audit Thomas Lamprecht
2026-09-23 20:59 ` [PATCH manager 6/9] ui: dc options: allow editing the API token policy Thomas Lamprecht
2026-09-23 20:59 ` [PATCH manager 7/9] ui: token edit: adapt to the datacenter " Thomas Lamprecht
2026-09-23 20:59 ` [PATCH proxmox 8/9] access-control: add API token policy type with expiry checks Thomas Lamprecht
2026-09-23 20:59 ` [PATCH proxmox 9/9] access-control: enforce token policy on token create and update 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=20260923210000.4031318-5-t.lamprecht@proxmox.com \
--to=t.lamprecht@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