From: Elias Huhsovitz <e.huhsovitz@proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Elias Huhsovitz <e.huhsovitz@proxmox.com>
Subject: [PATCH access-control 0/2] fix: #6510: Allow deleting ACLs for non-existent entities & add API tests
Date: Mon, 20 Jul 2026 15:45:33 +0200 [thread overview]
Message-ID: <20260720134535.136172-1-e.huhsovitz@proxmox.com> (raw)
This series fixes Bug #6510, which prevents the deletion of ACLs
for non-existent users, groups, or API tokens.
Patch 1/2 modifies the `update_acl` API endpoint to bypass the
entity existence check when the `delete` flag is set. This change
allows administrators to clean up orphaned ACLs without weakening the
strict validation applied when adding new permissions.
Patch 2/2 introduces automated tests for the
`PUT /access/acl` endpoint. The test suite verifies standard creation,
modification, and deletion workflows, enforces privilege boundaries,
and specifically tests the edge case resolved in the first patch.
Elias Huhsovitz (2):
fix #6510: api: acl: allow deleting ACLs for non-existent entities
test: api: add tests for ACL modification endpoint
src/PVE/API2/ACL.pm | 6 +-
src/test/api-tests.pl | 2 +-
src/test/api-update-acl-test.pl | 301 ++++++++++++++++++++++++++++++++
3 files changed, 305 insertions(+), 4 deletions(-)
create mode 100644 src/test/api-update-acl-test.pl
--
2.47.3
next reply other threads:[~2026-07-20 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 13:45 Elias Huhsovitz [this message]
2026-07-20 13:45 ` [PATCH access-control 1/2] fix #6510: api: acl: allow deleting ACLs for non-existent entities Elias Huhsovitz
2026-07-21 14:40 ` Daniel Kral
2026-07-20 13:45 ` [PATCH access-control 2/2] test: api: add tests for ACL modification endpoint Elias Huhsovitz
2026-07-21 15:20 ` Daniel Kral
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=20260720134535.136172-1-e.huhsovitz@proxmox.com \
--to=e.huhsovitz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.