From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 9E41060C3A for ; Thu, 3 Sep 2020 14:15:23 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 261F718DA8 for ; Thu, 3 Sep 2020 14:14:53 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 54DBD18D9E for ; Thu, 3 Sep 2020 14:14:52 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 1C5D9449F1 for ; Thu, 3 Sep 2020 14:14:52 +0200 (CEST) Date: Thu, 03 Sep 2020 14:14:41 +0200 From: Fabian =?iso-8859-1?q?Gr=FCnbichler?= To: Proxmox VE user list References: <88f905da-f9cc-4636-3f54-c653f48b78c4@ecos.de> In-Reply-To: <88f905da-f9cc-4636-3f54-c653f48b78c4@ecos.de> MIME-Version: 1.0 User-Agent: astroid/0.15.0 (https://github.com/astroidmail/astroid) Message-Id: <1599134462.pm42d9isdh.astroid@nora.none> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL 0.029 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust 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] Subject: Re: [PVE-User] User permissions for some hosts X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Sep 2020 12:15:23 -0000 On September 3, 2020 12:36 pm, Tobias Guth wrote: > Hi, >=20 > I have posted some issue on the pve forum regarding user permissions on > some pve hosts. > (https://forum.proxmox.com/threads/permission-set-for-specific-hosts.7513= 8/) >=20 > but no answer so far. >=20 > I try to give some usergroup the permission to create/delete/modify > virtual machines on just 2 hosts of our cluster. > But I have no luck to configure the right permissions that this group > can not modify or delete virtual machines on the hosts. > There is no namespace like /vms/nodes or /vms/node1, just /vms. permissions don't work on that level. you might be able to somewhat work=20 around it (e.g., with a storage that is only available on a subset of=20 nodes), but that is more of a hack than anything else. > Is there any way to configure this ? >=20 > And one more question. Was exatly does the propagade option with > permissions ? > Does it mean to propagade given permissions through out the cluster ? propagate means set this role on subpaths as well, unless they have a=20 more specific role set. e.g., if you give some role A to user X on path /vms with propagate set,=20 and additionally give role B to user X on path /vms/123, user X is 'A'=20 for all VMs except 123, where they are 'B'. on recent PVE versions, you=20 can use 'pveum user permissions' to get a list of effective permissions,=20 either for all paths with an ACL (also available as button in the User=20 management GUI), or for a specific path. =