Confluent Kafka messaging provider configuration
Learn about the configuration parameters required to use Confluent Kafka as a messaging provider in Reltio.
Confluent Kafka can be configured as a messaging provider for event streaming destinations. You can define the provider using either a provider alias configuration or a URI-based configuration.
Provider type values
The following provider type values define the authentication mechanism used to connect to Confluent Kafka:
| Type | Credentials required | Description |
|---|---|---|
| kafka-plain | Yes | Uses SASL/PLAIN authentication. |
| kafka-confluent-entraid | Yes | Uses SASL/OAUTHBEARER authentication with the OAuth 2.0 Client Credentials grant to connect to Confluent Cloud, with Azure Entra ID as the identity provider. |
URI-based configuration
Confluent Kafka providers are configured using a URI that defines the authentication type, credentials, and Kafka bootstrap server.
The URI format is:
kafka-plain://{username}:{password}@{host}:{port}
The username and password values must be URL-encoded if they contain special characters.
Here's an example for uri:
kafka-plain://my-api-key:my-api-secret@pkc-12345.us-east-1.aws.confluent.cloud:9092The Confluent Kafka provider URI contains the following components:
- Scheme: Defines the authentication type, for example
kafka-plainorkafka-confluent-entraid. - Username: Kafka API key, SASL username, or OAuth client ID.
- Password: Kafka API secret, SASL password, or OAuth client secret.
- Host and port: Confluent Kafka bootstrap server in
host:portformat.
Tenant configuration example
The Confluent Kafka provider is configured in the tenant messaging destinations using the provider URI.
{
"messaging": {
"destinations": [
{
"type": "queue",
"provider": "kafka-plain://<username>:<password>@<host>:<port>",
"name": "example",
"enabled": true
}
]
}
}