From: Shannon Sterz <s.sterz@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs v2] pveum: switch OATH 2.0 to the correct OAuth 2.0; use pve not Proxmox
Date: Tue, 4 Mar 2025 15:49:27 +0100 [thread overview]
Message-ID: <20250304144927.235339-1-s.sterz@proxmox.com> (raw)
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
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-03-04 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 14:49 Shannon Sterz [this message]
2025-03-04 15:35 ` [pve-devel] applied: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250304144927.235339-1-s.sterz@proxmox.com \
--to=s.sterz@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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