Pulsar supports authenticating clients using OAuth 2.0 access tokens. You can use OAuth 2.0 access tokens to identify a Pulsar client and associate the Pulsar client with some “principal” (or “role”), which is permitted to do some actions, such as publishing messages to a topic or consume messages from a topic.

This module is used to support the Pulsar client authentication plugin for OAuth 2.0. After communicating with the Oauth 2.0 server, the Pulsar client gets an access token from the Oauth 2.0 server, and passes this access token to the Pulsar broker to do the authentication. The broker can use the org.apache.pulsar.broker.authentication.AuthenticationProviderToken. Or, you can add your own AuthenticationProvider to make it with this module.

Authentication provider configuration

This library allows you to authenticate the Pulsar client by using an access token that is obtained from an OAuth 2.0 authorization service, which acts as a token issuer.

Authentication types

The authentication type determines how to obtain an access token through an OAuth 2.0 authorization flow.

Note

Currently, the Pulsar Java client only supports the client_credentials authentication type .

Client credentials

The following table lists parameters supported for the client credentials authentication type.

ParameterDescription示例Required or not
typeOauth 2.0 authentication type.client_credentials (default)Optional
issuerUrlURL of the authentication provider which allows the Pulsar client to obtain an access tokenhttps://accounts.google.comRequired
privateKeyURL to a JSON credentials fileSupport the following pattern formats:
  • file:///path/to/file
  • file:/path/to/file
  • data:application/json;base64,<base64-encoded value>
    		• Required
    audienceAn OAuth 2.0 “resource server” identifier for the Pulsar clusterhttps://broker.example.comRequired

    The credentials file contains service account credentials used with the client authentication type. The following shows an example of a credentials file credentials_file.json.

    1. {
    2.   "type": "client_credentials",
    3.   "client_id": "d9ZyX97q1ef8Cr81WHVC4hFQ64vSlDK3",
    4.   "client_secret": "on1uJ...k6F6R",
    5.   "client_email": "1234567890-abcdefghijklmnopqrstuvwxyz@developer.gserviceaccount.com",
    6.   "issuer_url": "https://accounts.google.com"
    7. }

    In the above example, the authentication type is set to client_credentials by default. And the fields “client_id” and “client_secret” are required.

    Typical original Oauth2 request mapping

    The following shows a typical original Oauth2 request, which is used to obtain the access token from the Oauth2 server.

    1. curl --request POST \
    2.   --url https://dev-kt-aa9ne.us.auth0.com/oauth/token \
    3.   --header 'content-type: application/json' \
    4.   --data '{
    5.   "client_id":"Xd23RHsUnvUlP7wchjNYOaIfazgeHd9x",
    6.   "client_secret":"rT7ps7WY8uhdVuBTKWZkttwLdQotmdEliaM5rLfmgNibvqziZ-g07ZH52N_poGAb",
    7.   "audience":"https://dev-kt-aa9ne.us.auth0.com/api/v2/",
    8.   "grant_type":"client_credentials"}'

    In the above example, the mapping relationship is shown as below.

    • The issuerUrl parameter in this plugin is mapped to --url https://dev-kt-aa9ne.us.auth0.com/oauth/token.
    • The privateKey file parameter in this plugin should at least contains the client_id and client_secret fields.
    • The audience parameter in this plugin is mapped to "audience":"https://dev-kt-aa9ne.us.auth0.com/api/v2/".

    Client Configuration

    You can use the Oauth2 authentication provider with the following Pulsar clients.

    Java

    You can use the factory method to configure authentication for Pulsar Java client.

    1. String issuerUrl = "https://dev-kt-aa9ne.us.auth0.com/oauth/token";
    2. String credentialsUrl = "file:///path/to/KeyFile.json";
    3. String audience = "https://dev-kt-aa9ne.us.auth0.com/api/v2/";
    5. PulsarClient client = PulsarClient.builder()
    6.     .serviceUrl("pulsar://broker.example.com:6650/")
    7.     .authentication(
    8.         AuthenticationFactoryOAuth2.clientCredentials(issuerUrl, credentialsUrl, audience))
    9.     .build();

    In addition, you can also use the encoded parameters to configure authentication for Pulsar Java client.

    1. Authentication auth = AuthenticationFactory
    2.     .create(AuthenticationOAuth2.class.getName(), "{"type":"client_credentials","privateKey":"./key/path/..","issuerUrl":"...","audience":"..."}");
    3. PulsarClient client = PulsarClient.builder()
    4.     .serviceUrl("pulsar://broker.example.com:6650/")
    5.     .authentication(auth)
    6.     .build();

    C++ client

    The C++ client is similar to the Java client. You need to provide parameters of issuerUrl, private_key (the credentials file path), and the audience.

    1. #include <pulsar/Client.h>
    3. pulsar::ClientConfiguration config;
    4. std::string params = R"({
    5.     "issuer_url": "https://dev-kt-aa9ne.us.auth0.com/oauth/token",
    6.     "private_key": "../../pulsar-broker/src/test/resources/authentication/token/cpp_credentials_file.json",
    7.     "audience": "https://dev-kt-aa9ne.us.auth0.com/api/v2/"})";
    9. config.setAuth(pulsar::AuthOauth2::create(params));
    11. pulsar::Client client("pulsar://broker.example.com:6650/", config);

    Go client

    To enable OAuth2 authentication in Go client, you need to configure OAuth2 authentication. This example shows how to configure OAuth2 authentication in Go client.

    1. oauth := pulsar.NewAuthenticationOAuth2(map[string]string{
    2.         "type":       "client_credentials",
    3.         "issuerUrl":  "https://dev-kt-aa9ne.us.auth0.com/oauth/token",
    4.         "audience":   "https://dev-kt-aa9ne.us.auth0.com/api/v2/",
    5.         "privateKey": "/path/to/privateKey",
    6.         "clientId":   "0Xx...Yyxeny",
    7.     })
    8. client, err := pulsar.NewClient(pulsar.ClientOptions{
    9.         URL:              "puslar://my-cluster:6650",
    10.         Authentication:   oauth,
    11. })