Skip to main content

Authentication using TLS

TLS Authentication Overview

TLS authentication is an extension of TLS transport encryption, but instead of only servers having keys and certs which the client uses to verify the server's identity, clients also have keys and certs which the server uses to verify the client's identity. You must have TLS transport encryption configured on your cluster before you can use TLS authentication. This guide assumes you already have TLS transport encryption configured.

Creating client certificates

Client certificates are generated using the same certificate authority as was used to generate the server certificates.

The biggest difference between client certs and server certs is that the common name for the client certificate is the role token which that client will be authenticated as.

First generate the key.

$ openssl genrsa -out admin.key.pem 2048

Similar to the broker, the client expects the key to be in PKCS 8 format, so convert it.

$ openssl pkcs8 -topk8 -inform PEM -outform PEM \
-in admin.key.pem -out admin.key-pk8.pem -nocrypt

Generate the certificate request. When asked for a common name, enter the role token which you want this key pair to authenticate a client as.

$ openssl req -config openssl.cnf \
-key admin.key.pem -new -sha256 -out admin.csr.pem


If there is no openssl.cnf, please read Certificate authority to get the openssl.cnf.

Sign with request with the certificate authority. Note that that client certs uses the usr_cert extension, which allows the cert to be used for client authentication.

$ openssl ca -config openssl.cnf -extensions usr_cert \
-days 1000 -notext -md sha256 \
-in admin.csr.pem -out admin.cert.pem

This will give you a cert, admin.cert.pem, and a key, admin.key-pk8.pem, which, with ca.cert.pem, can be used by clients to authenticate themselves to brokers and proxies as the role token admin.


If got "unable to load CA private key" error and the reason is "No such file or directory: /etc/pki/CA/private/cakey.pem" in this step. Please try :

$ cd /etc/pki/tls/misc/CA
$ ./CA -newca

to generate cakey.pem .

Enabling TLS Authentication ...

... on Brokers

To configure brokers to authenticate clients, put the following in broker.conf, alongside the configuration to enable tls transport:

# Configuration to enable authentication

# operations and publish/consume from all topics

# Authentication settings of the broker itself. Used when the broker connects to other brokers, either in same or other clusters

... on Proxies

To configure proxies to authenticate clients, put the following in proxy.conf, alongside the configuration to enable tls transport:

The proxy should have its own client key pair for connecting to brokers. The role token for this key pair should be configured in the proxyRoles of the brokers. See the authorization guide for more details.

# For clients connecting to the proxy

# For the proxy to connect to brokers

Client configuration

When TLS authentication, the client needs to connect via TLS transport, so you need to configure the client to use https:// and port 8443 for the web service URL, and pulsar+ssl:// and port 6651 for the broker service URL.

CLI tools

Command-line tools like pulsar-admin, pulsar-perf, and pulsar-client use the conf/client.conf config file in a Pulsar installation.

You'll need to add the following parameters to that file to use TLS authentication with Pulsar's CLI tools:


Java client

import org.apache.pulsar.client.api.PulsarClient;

PulsarClient client = PulsarClient.builder()

Python client

from pulsar import Client, AuthenticationTLS

auth = AuthenticationTLS("/path/to/my-role.cert.pem", "/path/to/my-role.key-pk8.pem")
client = Client("pulsar+ssl://",

C++ client

#include <pulsar/Client.h>

pulsar::ClientConfiguration config;

pulsar::AuthenticationPtr auth = pulsar::AuthTls::create("/path/to/my-role.cert.pem",

pulsar::Client client("pulsar+ssl://", config);