From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 3AA381FF15C for ; Fri, 17 Oct 2025 15:02:10 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id F1FAE3030; Fri, 17 Oct 2025 15:02:30 +0200 (CEST) From: Shan Shaji To: pdm-devel@lists.proxmox.com Date: Fri, 17 Oct 2025 15:02:10 +0200 Message-ID: <20251017130217.160313-1-s.shaji@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1760706140242 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.114 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com, vnets.rs, zones.rs, controllers.rs] Subject: [pdm-devel] [PATCH datacenter-manager v2 0/3] fix #6901: allow non root users to access the EVPN dashboard X-BeenThere: pdm-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Datacenter Manager development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Datacenter Manager development discussion Content-Type: multipart/mixed; boundary="===============8574808753475426877==" Errors-To: pdm-devel-bounces@lists.proxmox.com Sender: "pdm-devel" --===============8574808753475426877== Content-Type: text/plain; charset=yes Content-Transfer-Encoding: 8bit When a non-root user tried to access the EVPN section, the API was returning a "403: permission check failed" error. To fix this, explicit permission checks have been added for the `/zones`, `/vnets`, and `/controllers` endpoints. Now, every authenticated user can access these endpoints however, the user must have at least the Resource.Audit permission under `/resource`. Remotes are also filtered based on the user’s access. Lists will only be fetched from remotes for which the user has at least the `Resource.Audit` permission on `/remote/{remote_name}`. changes since v1: thanks @stefan patch: https://lore.proxmox.com/pdm-devel/DDKKKUCY3S4R.1FDPCH2742RY5@proxmox.com/T/#t - Removed unused import from vnets.rs file. Shan Shaji (3): fix #6901: api: add explicit permission check for controllers list fix #6901: api: add explicit permission check for vnets list fix #6901: api: add explicit permission check for zones list server/src/api/sdn/controllers.rs | 30 ++++++++++++++++++++++++++---- server/src/api/sdn/vnets.rs | 28 +++++++++++++++++++++++++--- server/src/api/sdn/zones.rs | 28 +++++++++++++++++++++++++--- 3 files changed, 76 insertions(+), 10 deletions(-) -- 2.47.3 --===============8574808753475426877== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ pdm-devel mailing list pdm-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel --===============8574808753475426877==--