From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-apiclient v4 1/1] try to refresh ticket before an api call
Date: Fri, 14 Nov 2025 15:59:16 +0100 [thread overview]
Message-ID: <20251114145927.3766668-2-d.csapak@proxmox.com> (raw)
In-Reply-To: <20251114145927.3766668-1-d.csapak@proxmox.com>
when the ticket is an hour old (or older).
This can help for long running tasks that reuse the api client
throughout the whole task.
It will not work though if there is more than 2 hours between api calls,
but that should not be the case that often.
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
src/PVE/APIClient/LWP.pm | 21 ++++++++++++++++++++-
1 file changed, 20 insertions(+), 1 deletion(-)
diff --git a/src/PVE/APIClient/LWP.pm b/src/PVE/APIClient/LWP.pm
index 7407dc4..f0c81bc 100755
--- a/src/PVE/APIClient/LWP.pm
+++ b/src/PVE/APIClient/LWP.pm
@@ -276,7 +276,26 @@ sub call {
my $ua = $self->{useragent};
- # fixme: check ticket lifetime?
+ if ($ticket && $ticket =~ m/^(\S+)::[^:\s]+$/) {
+ my $plain = $1;
+
+ # only the last 8 characters from the plain part are the timestamp
+ if ($plain =~ m/([A-Z0-9]{8})$/) {
+ my $timestamp = $1;
+ my $ttime = hex($timestamp);
+ my $age = time() - $ttime;
+
+ if ($age > 3600) { # older than one hour
+ if (!defined($self->{password})) {
+ $self->{password} = $ticket;
+ $self->login();
+ $self->{password} = undef;
+ } else {
+ $self->login();
+ }
+ }
+ }
+ }
if (!$ticket && !$apitoken && $self->{username} && $self->{password}) {
$self->login();
--
2.47.3
_______________________________________________
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-11-14 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 14:59 [pve-devel] [PATCH apiclient/common/manager v4 0/5] implement cluster-wide bulk-actions for guests Dominik Csapak
2025-11-14 14:59 ` Dominik Csapak [this message]
2025-11-14 14:59 ` [pve-devel] [PATCH common v4 1/1] json schema/rest environment: add 'expose_credentials' option Dominik Csapak
2025-11-14 14:59 ` [pve-devel] [PATCH manager v4 1/3] http server/pvesh: set credentials if necessary Dominik Csapak
2025-11-14 21:02 ` [pve-devel] applied: " Thomas Lamprecht
2025-11-14 14:59 ` [pve-devel] [PATCH manager v4 2/3] api: implement node-independent bulk actions Dominik Csapak
2025-11-14 21:02 ` [pve-devel] applied: " Thomas Lamprecht
2025-11-14 14:59 ` [pve-devel] [PATCH manager v4 3/3] ui: add bulk actions to the datacenter level Dominik Csapak
2025-11-14 21:02 ` [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=20251114145927.3766668-2-d.csapak@proxmox.com \
--to=d.csapak@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