public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
* [pve-devel] [PATCH docs] pveum: switch OATH 2.0 to the correct OAuth 2.0; use pve not Proxmox
@ 2025-02-27  9:42 Shannon Sterz
  2025-02-27 10:00 ` Thomas Lamprecht
  0 siblings, 1 reply; 4+ messages in thread
From: Shannon Sterz @ 2025-02-27  9:42 UTC (permalink / raw)
  To: pve-devel

this

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
-- 
2.39.5



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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [pve-devel] [PATCH docs] pveum: switch OATH 2.0 to the correct OAuth 2.0; use pve not Proxmox
  2025-02-27  9:42 [pve-devel] [PATCH docs] pveum: switch OATH 2.0 to the correct OAuth 2.0; use pve not Proxmox Shannon Sterz
@ 2025-02-27 10:00 ` Thomas Lamprecht
  2025-02-27 10:06   ` Shannon Sterz
  2025-03-04 14:52   ` Shannon Sterz
  0 siblings, 2 replies; 4+ messages in thread
From: Thomas Lamprecht @ 2025-02-27 10:00 UTC (permalink / raw)
  To: Proxmox VE development discussion, Shannon Sterz

Am 27.02.25 um 10:42 schrieb Shannon Sterz:
> this

this what?

> 
> 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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [pve-devel] [PATCH docs] pveum: switch OATH 2.0 to the correct OAuth 2.0; use pve not Proxmox
  2025-02-27 10:00 ` Thomas Lamprecht
@ 2025-02-27 10:06   ` Shannon Sterz
  2025-03-04 14:52   ` Shannon Sterz
  1 sibling, 0 replies; 4+ messages in thread
From: Shannon Sterz @ 2025-02-27 10:06 UTC (permalink / raw)
  To: Thomas Lamprecht, Proxmox VE development discussion

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.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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [pve-devel] [PATCH docs] pveum: switch OATH 2.0 to the correct OAuth 2.0; use pve not Proxmox
  2025-02-27 10:00 ` Thomas Lamprecht
  2025-02-27 10:06   ` Shannon Sterz
@ 2025-03-04 14:52   ` Shannon Sterz
  1 sibling, 0 replies; 4+ messages in thread
From: Shannon Sterz @ 2025-03-04 14:52 UTC (permalink / raw)
  To: Thomas Lamprecht, Proxmox VE development discussion

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2025-03-04 14:52 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-02-27  9:42 [pve-devel] [PATCH docs] pveum: switch OATH 2.0 to the correct OAuth 2.0; use pve not Proxmox Shannon Sterz
2025-02-27 10:00 ` Thomas Lamprecht
2025-02-27 10:06   ` Shannon Sterz
2025-03-04 14:52   ` Shannon Sterz

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal