From: Sven Scholle <sven@shelldog.de>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] Empty list as response of an API-endpoint
Date: Wed, 04 Jan 2023 16:10:00 +0100 [thread overview]
Message-ID: <0c01739ac2da8649dd9f96cc374ce84b@shelldog.de> (raw)
Hi,
I have a problem regarding the API rights management.
The following request returns an empty array when issued using a token
with the role PVEAuditor:
'pve.foo.bar:8006/api2/json/nodes/{}/storage/{}/content?content=backup&vmid={}'.format(node,
storage, vmid)
When I disable privilege seperation or use the role Administrator, I
will receive the content in the storage mathing the filters above.
Those permissions do not seem to be sufficient: "Sys.Audit Sys.Syslog
Pool.Audit VM.Audit Datastore.Audit"
Using the permissions above, I'd expect to be granted to use the
API-call above. I also tried "VM.Backup", but that didn't do the trick.
Did I forget a permission or is there a bug?
Used Proxmox-VE-Version: 7.2-1
Thanks!
Regards
Sven
next reply other threads:[~2023-01-04 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 15:10 Sven Scholle [this message]
2023-01-05 8:37 ` Fabian Grünbichler
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=0c01739ac2da8649dd9f96cc374ce84b@shelldog.de \
--to=sven@shelldog.de \
--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