From: Hannes Duerr <h.duerr@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-docs] api token: mention that guest/sys console cannot be accessed by an API token.
Date: Fri, 27 Feb 2026 11:26:12 +0100 [thread overview]
Message-ID: <20260227102612.41532-1-h.duerr@proxmox.com> (raw)
Signed-off-by: Hannes Duerr <h.duerr@proxmox.com>
---
pveum.adoc | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/pveum.adoc b/pveum.adoc
index 25e10ef..6219363 100644
--- a/pveum.adoc
+++ b/pveum.adoc
@@ -87,11 +87,15 @@ much more maintainable access control list.
API Tokens
----------
-API tokens allow stateless access to most parts of the REST API from another
-system, software or API client. Tokens can be generated for individual users
-and can be given separate permissions and expiration dates to limit the scope
-and duration of the access. Should the API token get compromised, it can be
-revoked without disabling the user itself.
+API tokens allow stateless access to most parts of the REST API from
+another system, software, or API client. Exceptions are endpoints that
+provide access to the VM or System console. These endpoints require
+user privileges and can not be accessed via API token.
+Tokens can be generated for individual users and can be given separate
+permissions and expiration dates to limit the scope and duration of
+the access. Should the API token get compromised, it can be revoked
+without disabling the user itself.
+
API tokens come in two basic types:
--
2.47.3
reply other threads:[~2026-02-27 10:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260227102612.41532-1-h.duerr@proxmox.com \
--to=h.duerr@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