Implementation with Oauth Authentication of the PulsarClientAuthenticationService. Provides Pulsar clients with the ability to authenticate against a secured Apache Pulsar broker endpoint.
Pulsar, client, security, authentication, Oauth
In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property supports the NiFi Expression Language.
| Display Name | API Name | Default Value | Allowable Values | Description |
|---|---|---|---|---|
| Audience | AUDIENCE | An OAuth 2.0 "resource server" identifier for the Pulsar cluster, e.g., https://broker.example.com Supports Expression Language: true (will be evaluated using variable registry only) | ||
| Issuer URL | ISSUER_URL | URL of the authentication provider which allows the Pulsar client to obtain an access token, e.g.,https://accounts.google.com Supports Expression Language: true (will be evaluated using variable registry only) | ||
| Private key file | PRIVATE_KEY_FILE | URL to a JSON credentials file, e.g., file:///path/to/file Supports Expression Language: true (will be evaluated using variable registry only) | ||
| Trusted Certificate Filename | Trusted Certificate Filename | The fully-qualified filename of the Trusted certificate. |