This is an automated email from the ASF dual-hosted git repository.

mmarshall pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git


The following commit(s) were added to refs/heads/main by this push:
     new a48cf9a7ade Improve OIDC client authentication docs (#557)
a48cf9a7ade is described below

commit a48cf9a7ade827d02dbdbdf0915a5b34c885219b
Author: Michael Marshall <[email protected]>
AuthorDate: Fri May 12 17:12:16 2023 -0500

    Improve OIDC client authentication docs (#557)
    
    * Improve OIDC client authentication docs
    
    * Apply suggestions from code review
    
    Co-authored-by: Jun Ma <[email protected]>
    
    ---------
    
    Co-authored-by: Jun Ma <[email protected]>
---
 docs/security-openid-connect.md                         | 2 +-
 versioned_docs/version-3.0.x/security-openid-connect.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/security-openid-connect.md b/docs/security-openid-connect.md
index 9b8026c4be7..ab7bf7fd8be 100644
--- a/docs/security-openid-connect.md
+++ b/docs/security-openid-connect.md
@@ -135,4 +135,4 @@ In order to simplify migration from Static JWTs to OIDC 
Authentication, it is po
 
 ## Configure OIDC authentication in Pulsar Clients and CLI Tools
 
-See the [OAuth2](security-oauth2.md) documentation for configuring clients to 
use OAuth2 authentication.
+The Pulsar OAuth2 client plugin can be used for clients that rely on the 
Client Credentials Flow for OIDC. See the [OAuth2 
Client](security-oauth2.md#configure-oauth2-authentication-in-pulsar-clients) 
documentation for configuring clients to integrate with Pulsar Servers running 
with the OIDC Authentication Provider.
diff --git a/versioned_docs/version-3.0.x/security-openid-connect.md 
b/versioned_docs/version-3.0.x/security-openid-connect.md
index f0d7221e86e..4f7cfd6985f 100644
--- a/versioned_docs/version-3.0.x/security-openid-connect.md
+++ b/versioned_docs/version-3.0.x/security-openid-connect.md
@@ -139,4 +139,4 @@ In order to simplify migration from Static JWTs to OIDC 
Authentication, it is po
 
 ## Configure OIDC authentication in Pulsar Clients and CLI Tools
 
-See the [OAuth2](security-oauth2.md) documentation for configuring clients to 
use OAuth2 authentication.
+The Pulsar OAuth2 client plugin can be used for clients that rely on the 
Client Credentials Flow for OIDC. See the [OAuth2 
Client](security-oauth2.md#configure-oauth2-authentication-in-pulsar-clients) 
documentation for configuring clients to integrate with Pulsar Servers running 
with the OIDC Authentication Provider.

Reply via email to