Skip to main content
Note: With this connector, you can authenticate either to or to Azure Event Hubs.

Apache Kafka コネクタを追加

Apache Kafka への認証

After you add the connector, you need to set the required properties. Bootstrap Servers: Enter the address of the Bootstrap servers to which you want to connect. supports authenticating to in several ways. Select your authentication method below to proceed to the relevant section that contains the authentication details.

None

Plain

SCRAM

To connect with SCRAM (SHA-256) credentials, specify these properties:
  • Auth Scheme: Select SCRAM.
  • User: Enter the username that you use to authenticate to your account.
  • Password: Enter the password that you use to authenticate to your account.

SCRAM-SHA-512

To connect with the SCRAM (SHA-512) credentials, specify these properties:
  • Auth Scheme: Select SCRAM-SHA-512.
  • User: Enter the username that you use to authenticate to your account.
  • Password: Enter the password that you use to authenticate to your account.

Kerberos

To connect with Kerberos, specify these properties:
  • Auth Scheme: Select Kerberos.
  • Kerberos SPN: Enter the service principal name (SPN) for the Kerberos domain controller.
  • Kerberos Service Name: Enter the name of the Kerberos service with which you want to authenticate.
  • (Optional) Kerberos Keytab File: Enter the keytab file that contains your pairs of the Kerberos principals and encrypted keys.
  • (Optional) Use Kerberos Ticket Cache: Select True to use a ticket cache with the logged-in user instead of a keytab file. The default value is False.

Azure Event Hubs への認証

After you add the connector, you need to set the following required properties to connect to Azure Event Hubs: For Bootstrap Servers, enter the address of the bootstrap servers to which you want to connect. supports authenticating to Apache Event Hubs in several ways. Select your authentication method below to proceed to the relevant section that contains the authentication details.

SSL Certificate

To connect with a Secure Sockets Layer (SSL) client certificate, specify these properties:
  • Auth Scheme: Select SSLCertificate.
  • SSL Client Cert: Enter the SSL client certificate that is used to validate to the broker.
  • SSL Client Cert Type: Select the format of the SSL client certificate that is used to connect to the broker:
    • JKSFILE
    • PFXFILE
    • PEMKEY_FILE (default)
    • PEMKEY_BLOB
  • (Optional) SSL Client Cert Password: Enter the password that is used to decrypt the SSL client certificate.

Azure Active Directory

To connect with Azure Active Directory (AD) credentials, specify the following properties:
  • Azure Tenant: Enter the Microsoft Online tenant that is used to access data. If you do not specify a tenant, uses the default tenant.
  • OAuth Client Id: Enter the client Id that you were assigned when you registered your application with an OAuth authorization server.
  • OAuth Client Secret: Enter the client secret that you were assigned when you registered your application with an OAuth authorization server.

Azure Managed Service Identity

Azure Service Principal

Azure Service Principal Certificate

GCP Kafka への認証

After you add the connector, you need to set the following required properties to connect to GCP Kafka: For Bootstrap Servers, enter the address of the bootstrap servers to which you want to connect. supports authenticating to GCP Kafka in several ways. Select your authentication method below to proceed to the relevant section that contains the authentication details.

OAuth JWT

To connect with a account using OAuth JWT, specify the following properties:
  • Auth Scheme: Select OAuthJWT.
  • OAuth Client Id: Enter the client Id that you were assigned when you registered your application with an OAuth authorization server.
  • OAuth Client Secret: Enter the client secret that you were assigned when you registered your application with an OAuth authorization server.
  • OAuth JWT Cert: Enter your JSON web tokens (JWT) certificate store.
  • OAuth JWT Cert Type: Enter the type of key store that contains your JWT certificate. The default type is PEMKEY_BLOB.
  • OAuth JWT Cert Password: Enter the password for the OAuth JWT certificate that is used to access a password-protected certificate store. If the certificate store does not require a password, leave this property blank.
  • (Optional) OAuth JWT Cert Subject: Enter the subject of your OAuth JWT certificate.

GCP Instance Account

AWS Workload Identity

Extracting Metadata from Topics

models topics as tables and messages as rows. The Type Detection Scheme property controls how reads schema information from each topic. Details about Type Detection Scheme are provided in Complete Your Connection.

Schema Registry

The schema registry contains a list of topics that have registered schemas. The list of tables and columns are simply read directly from the schema registry. To connect to a service with a schema registry, specify the following properties:
  • Bootstrap Servers: Enter the server (host name or IP address) and port (in the format Server:Port) of the bootstrap servers.
  • Type Detection Scheme: Select the detection scheme that you want to use. For complete details about using this scheme, see Complete Your Connection.
  • (Optional) Schema Merge Mode: Select the mode by which you want to merge multiple schemas.
    • None (default)
    • Simple

Confluent Schema Registry

When you connect to Confluent Cloud, the registry URL corresponds to the Schema Registry endpoint value that is located in Schemas > Schema Registry > Instructions. The Confluent schema registry supports several authentication options. Typically, Confluent Cloud deployments require that you set the Registry Auth Scheme property to Basic, along with a registry user and registry password. To find your user and password, navigate to Schemas > Schema Registry > API Access and locate the access-key and secret-key values. On-premises deployments might not require authentication. In these configurations, you should set Registry Auth Scheme to None. These deployments might require SSL client certificates also. For that, you need to set the SSL Certificate registry auth scheme as well as the Registry Client Cert and Registry Client Cert Type options.

Amazon Web Services (AWS) Glue Schema Registry

When you connect to AWS Glue, the registry URL corresponds to the Amazon Resources Name (ARN) value of the registry. The AWS Glue schema registry only supports the Basic registry auth scheme. You should set Registry User and Registry Password, respectively, to the access key and secret key of a user that has access to the registry.

Topic Routing

You can control how source tables map to topics when you create a job that uses the destination. To do so, select one of the following options in the Add Job dialog when you create a job:
  • One topic per source table: Each source table is written to its own topic. automatically names the topic using the format SchemaName_TableName. If the source does not have a schema, the topic name is simply the table name.
  • All data to a single named topic: All source data for a table is written to one topic. When you select this option, a Topic field is displayed, as shown below. You can either enter a topic name in the field or search and select a topic, if a topic list is available. Add Job dialog showing the Topic field for a single named topic
If a target topic does not exist when the job runs, either creates it automatically or returns an error, depending on your broker configuration.

Message Partitioning

In , new destination jobs automatically partition messages by the source table’s primary key. This behavior controls how messages are distributed across partitions in the target topic.
  • Single primary key: uses the primary key value as the message key. All messages with the same key value are written to the same partition, so downstream consumers see changes for a given key in the order they were written.
  • No primary key: distributes messages across partitions in a round-robin pattern (each message goes to the next partition in sequence). No message key is assigned.
  • Automatic key-based partitioning does not support tables with composite (multiple-column) primary keys. To partition by a single key, update your query to include only one primary key column.
  • Existing destination jobs (prior to release 26.3) are not affected by this change.

接続を完了する

To complete your connection:
  1. Specify the following properties:
    • Type Detection Scheme: Select the detection scheme that you want to use.
      • (Default) RowScan—Scans messages from the topic to infer column names and data types. No additional configuration is required.
      • SchemaRegistry—Reads schema definitions from a Confluent-compatible schema registry. When you select this option, additional schema registry properties appear. For this scheme, specify the following properties:
        • Registry Url: Enter the URL to the server for the schema registry. When you specify this property, reads the schema from the server.
        • Registry Service: Select the Schema Registry service that you want to use for working with topic schemas.
          • Confluent (default)
          • AWSGlue
        • Registry Auth Scheme: Select the scheme that you want to use to authenticate to the schema registry.
          • (Default) None: This scheme specifies that no authentication is used.
          • Basic: For this scheme, specify the following properties:
            • Registry User: Enter the username that you use to authenticate with the server that you specified earlier for Registry Url.
            • Registry Password: Enter the password that you use to authenticate with the server that you specified earlier for Registry Url.
          • SSLCertificate: This scheme specifies that SSL client-certificate authentication should be used. For this setting, you must specify the following:
            • Registry Client Cert: Enter the TLS/SSL client certificate store for SSL client authentication (two-way SSL) with the schema registry.
            • (Optional) Registry Client Cert Password: Enter the password for your TLS/SSL client certificate.
            • (Optional) Registry Client Cert Subject Enter the subject of your TLS/SSL client certificate.
    • Use SSL: Select whether you want to enable Secure Sockets Layer (SSL). By default, the Enable checkbox is not selected.

詳細について