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?
hm strange, sorry that seems to have gotten cut of:
this switches the use of OATH 2.0 to the correct spelling of OAuth 2.0.
it also makes it clear that the OpenID Connect Discovery protocol is
used by Proxmox VE the product, not Proxmox the company. otherwise,
users could have gotten the impression that data is processed on company
servers.
>
>>
>> Signed-off-by: Shannon Sterz <s.st...@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
