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

sijie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git


The following commit(s) were added to refs/heads/master by this push:
     new f0df253  [docs] Fix link issue for "Authentication and authorization 
in Pulsar"  (#5771)
f0df253 is described below

commit f0df25308d274cd9358a4bf9195aa4f0244f4d9c
Author: belinda-wong <30765197+belinda-w...@users.noreply.github.com>
AuthorDate: Mon Dec 2 00:47:20 2019 +0800

    [docs] Fix link issue for "Authentication and authorization in Pulsar"  
(#5771)
    
    * Fixes the dead link
    
    changed to:
    see ["Enabling TLS Authentication on 
Proxies"](security-tls-authentication.md#enable-tls-authentication-on-proxies)
---
 site2/docs/security-authorization.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site2/docs/security-authorization.md 
b/site2/docs/security-authorization.md
index 6a1f015..60d4f1a 100644
--- a/site2/docs/security-authorization.md
+++ b/site2/docs/security-authorization.md
@@ -30,7 +30,7 @@ You can also enable the authorization for the proxy in the 
proxy configuration f
 
 ### Proxy Roles
 
-By default, the broker treats the connection between a proxy and the broker as 
a normal user connection. The broker authenticates the user as the role 
configured in `proxy.conf`(see ["Enabling TLS Authentication on 
Proxies"](security-tls-authentication#on-proxies)). However, when the user 
connects to the cluster through a proxy, the user rarely requires the 
authentication. The user expects to be able to interact with the cluster as the 
role for which they have authenticated with the proxy.
+By default, the broker treats the connection between a proxy and the broker as 
a normal user connection. The broker authenticates the user as the role 
configured in `proxy.conf`(see ["Enable TLS Authentication on 
Proxies"](security-tls-authentication.md#enable-tls-authentication-on-proxies)).
 However, when the user connects to the cluster through a proxy, the user 
rarely requires the authentication. The user expects to be able to interact 
with the cluster as the role for which they have  [...]
 
 Pulsar uses *Proxy roles* to enable the authentication. Proxy roles are 
specified in the broker configuration file, 
[`conf/broker.conf`](reference-configuration.md#broker). If a client that is 
authenticated with a broker is one of its ```proxyRoles```, all requests from 
that client must also carry information about the role of the client that is 
authenticated with the proxy. This information is called the *original 
principle*. If the *original principle* misses, the client is not able to [...]
 

Reply via email to