From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
	by lore.proxmox.com (Postfix) with ESMTPS id C99B41FF168
	for <inbox@lore.proxmox.com>; Tue,  4 Mar 2025 15:52:40 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id C8C99291A;
	Tue,  4 Mar 2025 15:52:36 +0100 (CET)
Mime-Version: 1.0
Date: Tue, 04 Mar 2025 15:52:03 +0100
Message-Id: <D87KEUOTRJE9.2BI50YD97E7Q6@proxmox.com>
To: "Thomas Lamprecht" <t.lamprecht@proxmox.com>, "Proxmox VE development
 discussion" <pve-devel@lists.proxmox.com>
From: "Shannon Sterz" <s.sterz@proxmox.com>
X-Mailer: aerc 0.20.1-0-g2ecb8770224a-dirty
References: <20250227094200.50802-1-s.sterz@proxmox.com>
 <a9738e0b-c645-42ac-96db-a2774482f544@proxmox.com>
In-Reply-To: <a9738e0b-c645-42ac-96db-a2774482f544@proxmox.com>
X-SPAM-LEVEL: Spam detection results:  0
 AWL -0.013 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
 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] [PATCH docs] pveum: switch OATH 2.0 to the correct
 OAuth 2.0; use pve not Proxmox
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>

On Thu Feb 27, 2025 at 11:00 AM CET, Thomas Lamprecht wrote:
> Am 27.02.25 um 10:42 schrieb Shannon Sterz:
>> this
>
> this what?

sent a v2 to fix this:

Superseeded-by: https://lore.proxmox.com/pve-devel/20250304144927.235339-1-s.sterz@proxmox.com/

>
>>
>> Signed-off-by: Shannon Sterz <s.sterz@proxmox.com>
>> ---
>>  pveum.adoc | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/pveum.adoc b/pveum.adoc
>> index 81565ab..0cc267e 100644
>> --- a/pveum.adoc
>> +++ b/pveum.adoc
>> @@ -160,7 +160,7 @@ as an authentication protocol.
>>
>>  OpenID Connect::
>>
>> -OpenID Connect is implemented as an identity layer on top of the OATH 2.0
>> +OpenID Connect is implemented as an identity layer on top of the OAuth 2.0
>>  protocol. It allows clients to verify the identity of the user, based on
>>  authentication performed by an external authorization server.
>>
>> @@ -436,7 +436,7 @@ OpenID Connect
>>  The main OpenID Connect configuration options are:
>>
>>  * `Issuer URL` (`issuer-url`): This is the URL of the authorization server.
>> -Proxmox uses the OpenID Connect Discovery protocol to automatically configure
>> +{pve} uses the OpenID Connect Discovery protocol to automatically configure
>>  further details.
>>  +
>>  While it is possible to use unencrypted `http://` URLs, we strongly recommend to



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel