From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Shan Shaji" <s.shaji@proxmox.com>, <pdm-devel@lists.proxmox.com>
Subject: Re: [PATCH datacenter-manager v3 1/6] server: pbs-client: add delete admin token method
Date: Fri, 13 Feb 2026 14:20:01 +0100 [thread overview]
Message-ID: <DGDV4VVRHS7S.100VHZBKJ6BXB@proxmox.com> (raw)
In-Reply-To: <20260211152016.445817-2-s.shaji@proxmox.com>
Hi Shan,
thanks for the patch!
On Wed Feb 11, 2026 at 4:20 PM CET, Shan Shaji wrote:
> Inorder to allow deleting the generated token of PBS from PDM, add
> method inside the PbsClient to delete the admin token.
>
> Signed-off-by: Shan Shaji <s.shaji@proxmox.com>
> ---
>
> changes since v2: No changes
> changes since v1:
> - Revert the dropping of '/' from the comment.
> - Remove unnecessary colon.
>
> server/src/pbs_client.rs | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/server/src/pbs_client.rs b/server/src/pbs_client.rs
> index f4f1f82..31befdd 100644
> --- a/server/src/pbs_client.rs
> +++ b/server/src/pbs_client.rs
> @@ -260,6 +260,13 @@ impl PbsClient {
> Ok(token)
> }
>
> + /// Delete API-Token from the PBS remote.
tiny nit: I'd spell it 'API token'
> + pub async fn delete_admin_token(&self, userid: &Userid, tokenid: &str) -> Result<(), Error> {
This function should take &TokenameRef, I think. After all, it's what
you have at the callsite before you you turn it into a &str.
Also, I think the function should just be called `delete_token`, since
nothing of it is specific to the token being an admin token (it can
delete *any* token, not just an admin one). That being said, I
understand why you named it this way, it's the symmetry with
`create_admin_token`. The difference is that `create_admin_token` does
indeed create a new token *and* also assigns admin permissions to it.
> + let path = format!("/api2/extjs/access/users/{userid}/token/{tokenid}");
Technically, the userid parameter should be percent-encoded - the @ sign
in "root@pam" would usually be reserved to separate credentials and the
host in a URL, see [1]. Apparently its not an issue with the
`create_admin_token` function so far, but still a good practice, even if
we don't really have issues with it now.
[1] https://docs.mapp.com/docs/url-encoding-and-what-characters-are-valid-in-a-uri
> + self.0.delete(&path).await?.nodata()?;
> + Ok(())
> + }
> +
> /// Return the status the Proxmox Backup Server instance
> pub async fn node_status(&self) -> Result<pbs_api_types::NodeStatus, Error> {
> let path = "/api2/extjs/nodes/localhost/status";
next prev parent reply other threads:[~2026-02-13 13:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 15:20 [PATCH datacenter-manager/proxmox v3 0/7] fix #6914: add option to remove already existing token Shan Shaji
2026-02-11 15:20 ` [PATCH datacenter-manager v3 1/6] server: pbs-client: add delete admin token method Shan Shaji
2026-02-13 13:20 ` Lukas Wagner [this message]
2026-02-11 15:20 ` [PATCH datacenter-manager v3 2/6] server: api: add support to optionally delete token from remote Shan Shaji
2026-02-13 13:20 ` Lukas Wagner
2026-02-11 15:20 ` [PATCH datacenter-manager v3 3/6] pdm-client: accept `delete-token` argument for deleting api token Shan Shaji
2026-02-13 13:20 ` Lukas Wagner
2026-02-11 15:20 ` [PATCH datacenter-manager v3 4/6] cli: client: add `delete-token` option to delete token from remote Shan Shaji
2026-02-13 13:21 ` Lukas Wagner
2026-02-11 15:20 ` [PATCH datacenter-manager v3 5/6] fix: ui: add remove confirmation dialog with optional token deletion Shan Shaji
2026-02-13 13:21 ` Lukas Wagner
2026-02-11 15:20 ` [PATCH datacenter-manager v3 6/6] cli: admin: add `delete-token` option to delete token from remote Shan Shaji
2026-02-13 13:21 ` Lukas Wagner
2026-02-11 15:20 ` [PATCH proxmox v3 1/1] pve-api-types: generate missing `delete_token` method Shan Shaji
2026-02-13 13:19 ` [PATCH datacenter-manager/proxmox v3 0/7] fix #6914: add option to remove already existing token Lukas Wagner
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=DGDV4VVRHS7S.100VHZBKJ6BXB@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=pdm-devel@lists.proxmox.com \
--cc=s.shaji@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