You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2018/10/24 06:35:01 UTC

[GitHub] jai1 opened a new issue #2830: Inter Broker communication TLS not working for Pulsar Admin Client

jai1 opened a new issue #2830: Inter Broker communication TLS not working for Pulsar Admin Client 
URL: https://github.com/apache/pulsar/issues/2830
 
 
   #### Expected behavior
   
   Pulsar Admin Client in Broker should use TLS and connect to webServicePortTls.
   
   #### Actual behavior
   
   Pulsar Admin Client uses only the webServicePort 
   
   #### Steps to reproduce
   
   A. Create a cluster with TLS enabled in brokers
   B. Use AuthenticationTLS as brokerClientAuthPlugin
   C. run `pulsar-client-admin persistent list ...` 
   D. You will see a 500 response and "Authentication required" Error on the broker.
   
   #### System configuration
   **Pulsar version**: 2.2.1
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services