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 8A308748A0 for ; Wed, 2 Jun 2021 12:49:07 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7D4DAA129 for ; Wed, 2 Jun 2021 12:49:07 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (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 ABFC4A11B for ; Wed, 2 Jun 2021 12:49:03 +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 7033E436FB; Wed, 2 Jun 2021 12:49:03 +0200 (CEST) Date: Wed, 2 Jun 2021 12:48:15 +0200 (CEST) From: Dietmar Maurer To: wb , Proxmox VE development discussion Message-ID: <966663888.3483.1622630895184@webmail.proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 Importance: Normal X-Mailer: Open-Xchange Mailer v7.10.5-Rev11 X-Originating-Client: open-xchange-appsuite X-SPAM-LEVEL: Spam detection results: 0 AWL -0.044 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_NUMSUBJECT 0.5 Subject ends in numbers excluding current years 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-devel] =?utf-8?b?UkXCoDogUkXCoDogIFtQQVRDSF0gW1BBVENIIHB2?= =?utf-8?q?e-access-control=5D_SSO_feature=3Alogin_with_SAMLv2?= X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2021 10:49:07 -0000 > On 06/02/2021 12:16 PM wb wrote: > > > > I also wonder why SAML? Would it be an option to use OpenId connect instead? > As I was able to use SAML, I know the functional part and therefore, if I used SAML, it is only by ease. > > Switch to OpenID, why not. The time I set up a functional POC. > > On the other hand, I would like to know your constraints. Sorry, what do you want to know exactly? > Do you still want to use Rust? Yes. But I am still searching for usable crates: openidconnect: https://github.com/ramosbugs/openidconnect-rs Seems promising, but I have not done any testing so far... > If yes, I am curious to know how to bind perl to Rust? Do you have an example? https://git.proxmox.com/?p=perlmod.git;a=summary Hope the inline docs and examples are good enough to start... > I noticed from our exchange : > During an API call, if the user is not authenticated, do not pass in private and privileged the writing on /tmp/. yes, unprivileged users should not be able to write anything.