Connect Clusters
Connect clusters are required when using MirrorMaker 2 or Confluent Replicator as your replication tool. These clusters host the replication connectors that move data between Kafka clusters.
Connect Cluster Summary
Section titled “Connect Cluster Summary”The summary page displays all registered Connect clusters with their validation status. Use the search bar to locate a specific cluster.
Adding a Connect Cluster
Section titled “Adding a Connect Cluster”Click Add Connect Cluster to open the registration form.
Basic Information
Section titled “Basic Information”| Field | Required | Description |
|---|---|---|
| Cluster Alias | Yes | A unique name for the Connect cluster. |
| Description | No | Optional description of the cluster. |
| Tags | No | Optional tags for organization. |
| REST Endpoint | Yes | The URL of the Kafka Connect REST API. |
SSL Certificate Locations
Section titled “SSL Certificate Locations”If SSL is enabled on the Connect cluster, provide the certificate file paths as they exist on the Connect cluster host:
| Field | Description |
|---|---|
| Source Keystore Location | Location of the keystore file on the source Connect worker. |
| Source Truststore Location | Location of the truststore file on the source Connect worker. |
| Destination Keystore Location | Location of the keystore file on the destination Connect worker. |
| Destination Truststore Location | Location of the truststore file on the destination Connect worker. |
Authentication
Section titled “Authentication”Select the authentication method that matches your Connect cluster’s REST API configuration.
No authentication is required for the Connect REST API.
Standard username and password authentication.
| Field | Required | Description |
|---|---|---|
| Username | Yes | Connect REST API username. |
| Password | Yes | Connect REST API password. |
API key-based authentication.
| Field | Required | Description |
|---|---|---|
| API Key | Yes | The API key for authentication. |
| API Secret | Yes | The API secret for authentication. |
OAuth 2.0 or bearer token authentication. Toggle between two modes:
Direct Token Mode: Provide a pre-obtained bearer token.
OAuth Endpoint Mode:
| Field | Required | Description |
|---|---|---|
| Token Endpoint | Yes | The OAuth 2.0 token endpoint URL. |
| Client ID | Yes | The OAuth client identifier. |
| Client Secret | Yes | The OAuth client secret. |
| Grant Type | Yes | The OAuth grant type. Supported values: client_credentials, password, refresh_token. |
| Scope | No | OAuth scope to request. |
| Audience | No | Target audience for the token. |
SSL/TLS Truststore (optional)
If the OAuth token endpoint requires SSL verification with a custom certificate authority, provide the truststore configuration:
| Field | Required | Description |
|---|---|---|
| SSL Truststore File | No | Upload a truststore file for verifying the token endpoint’s SSL certificate. |
| SSL Truststore Password | No | Password for the truststore file. |
Certificate-based authentication using SSL/TLS client certificates. Three certificate formats are supported.
JKS (Java KeyStore)
| Field | Required | Description |
|---|---|---|
| Keystore File | Yes | Upload the JKS keystore file. |
| Keystore Password | Yes | Password for the keystore. |
| Truststore File | Yes | Upload the JKS truststore file. |
| Truststore Password | Yes | Password for the truststore. |
PKCS12
| Field | Required | Description |
|---|---|---|
| Keystore File | Yes | Upload the PKCS12 keystore file. |
| Keystore Password | Yes | Password for the keystore. |
| Truststore File | Yes | Upload the PKCS12 truststore file. |
| Truststore Password | Yes | Password for the truststore. |
PEM
| Field | Required | Description |
|---|---|---|
| CA Certificate File | Yes | Upload the CA certificate in PEM format. |
| Client Certificate File | Yes | Upload the client certificate in PEM format. |
| Client Key File | Yes | Upload the client private key in PEM format. |
| Client Key Password | No | Password for the client private key, if the key is encrypted. |
Testing the Connection
Section titled “Testing the Connection”After configuring the Connect cluster, click Test Connection to verify that the suite can reach the Connect REST API with the provided credentials.
Managing Connect Clusters
Section titled “Managing Connect Clusters”Editing a Cluster
Section titled “Editing a Cluster”Click the three-dot menu on any cluster row and select Edit to modify its configuration. You can also re-test the connection from the edit view.
Deleting a Cluster
Section titled “Deleting a Cluster”Click the three-dot menu and select Delete. A confirmation dialog is displayed before the cluster is removed.
