pulsar-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [pulsar] shiv4289 opened a new issue #4441: Like PulsarClient.buiilder, ClientConfigurationData.java should enable tls if pulsar+ssl
Date Mon, 03 Jun 2019 05:50:01 GMT
shiv4289 opened a new issue #4441: Like PulsarClient.buiilder, ClientConfigurationData.java
should enable tls if  pulsar+ssl 
URL: https://github.com/apache/pulsar/issues/4441
 
 
   **Describe the bug**
   There are two ways of instantiating a java client and both should behave in similar ways.
As of now, PulsarClient.builder assumes tls enabled if the pulsar+ssl or https is used in
the service url. In fact, the builder marks enableTls() as deprecated.
   
   ClientConfigurationData.java lags a bit that way. It does not enable tls if pulsar+ssl
or https is used in service url.
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1. Initialise PULSAR_BROKER_URL as pulsar+ssl:// *
   2. Instantiate the pulsar client with client config POJO.
   
   >             ClientConfigurationData clientConfig = new ClientConfigurationData();
   >             clientConfig.setServiceUrl(PULSAR_BROKER_URL);
   >             clientConfig.setTlsTrustCertsFilePath(PULSAR_CA_CERT_PATH);
   > 
   >             client = new PulsarClientImpl(clientConfig);
   
   **Expected behavior**
   Client should use tls if service url is pulsar+ssl://* or https://*
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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

Mime
View raw message