Kafka SSL Account

In this article

Overview

You can use the Kafka account type to connect Confluent Kafka Snaps with data sources that use Kafka SSL accounts.

Prerequisites

None.

Limitations and Known Issues

None.

Account Settings

  • Asterisk ( * ): Indicates a mandatory field.

  • Suggestion icon (): Indicates a list that is dynamically populated based on the configuration.

  • Expression icon ( ): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.

  • Add icon ( ): Indicates that you can add fields in the field set.

  • Remove icon ( ): Indicates that you can remove fields from the field set.

  • Upload icon ( ): Indicates that you can upload files.

Field Name

Field Type

Description

Field Name

Field Type

Description

Label*


Default Value: N/A
Example: Kafka SSL Account

String

Specify a unique label for the account.

Bootstrap Servers

Use this field set to configure a list of Bootstrap servers. 

Bootstrap Server

 

Default Value: N/A
Example: ec2-55-334-44-55.compute-1.amazonaws.com:9000

String/Expression

Specify the host:port pairs to be used for establishing the initial connection to the Kafka cluster.

Schema Registry URL


Default Value: N/A
Example: http://ec2-55-334-44-58.compute-1.amazonaws.com:8000

String/Expression

Specify the schema registry server URL.

Advanced Kafka Properties

Use this field set to specify any additional Kafka properties for connecting to the Kafka server that are not explicitly provided in the Confluent Kafka Snaps. 

  • You can use advanced properties to set Kafka properties that are not explicitly set in the Kafka Snaps. However, if you set the same properties in the Kafka Snaps and the advanced properties, then the Snap properties are used by the Pipeline. These properties are passed directly to the server and are not tested by SnapLogic, Inc.

  • If your Kafka SSL account requires a Truststore and Keystore file, use files in JKS format. Files in the PKCS12 format are also supported, but you must specify their format in the Advanced Kafka Properties section.

    • If your Truststore file is in PKCS12 format (which typically has a .p12 extension), add a row with Key=ssl.truststore.type and Value=PKCS12

    • If you also have a Keystore file in PKCS12 format, add a row with Key=ssl.keystore.type and Value=PKCS12

Key 

 

Default Value: N/A
Example: Customer2

String/Expression

Specify the key for any Kafka parameters that are not explicitly supported by the Snaps.

Value

 

Default Value: N/A
Example: 600

String/Expression/Integer

Specify the value for the corresponding key that is not explicitly supported by the Snaps.

Security Protocol


Default Value: SSL
Example: SASL_PLAINTEXT

String/Expression/Suggestion

Select the security protocol from the drop-down list. The available options are:

  • SSL

  • SASL_SSL

  • SASL_PLAINTEXT

Truststore Filepath


Default Value: N/A
Example: kafka.net.ssl.truststore

String/Expression

Select the location of the Truststore file that is used to authenticate the server.

Truststore Password


Default Value: N/A
Example: test1234

String/Expression

Specify the password for the Truststore file.

Keystore Filepath


Default Value: N/A
Example: :\var\private\ssl\kafka.client.keystore.jks

String/Expression

Select the location of Keystore filepath of the client.

Keystore File Password


Default Value: N/A
Example: d$ra0W$$#p!9

String/Expression

Specify the Keystore password to access the Keystore file that is used for client authentication. The keystore file contains the private key of the certificate; hence, it needs to be secure.

SSL Key Password


Default Value: N/A
Example: password3

String/Expression

Specify the SSL password of the private key in the SSL key store file.

SASL Properties

Use this field set to specify the account properties that are used for the security protocols.

SASL Mechanism

 

Default Value: PLAIN
Example: SCRAM-SHA-512

String/Expression/Suggestion

Select the SASL authentication mechanism for the account from the list. The available options are:

  • PLAIN

  • SCRAM-SHA-256

  • SCRAM-SHA-512

SASL Username or Key

 

Default Value: N/A
Example: Admin

String/Expression

Activates when you select SASL_SSL or SASL_PLAINTEXT for Security Protocol. Specify the username for the SASL security protocol.
To connect to Confluent Cloud, enter the API Key.

To set up an account for Confluent Cloud:

  • The Security Protocol must be set to SASL_SSL.

  • The SASL Username or Key and SASL Password or Secret should be set to the Key and Secret obtained from the Confluent Control center.

  • The SASL Mechanism must be PLAIN.

SASL Password or Secret

 

Default Value: N/A
Example: password4

String/Expression

Activates when you select SASL_SSL or SASL_PLAINTEXT for Security ProtocolSpecify the password for the SASL security protocol.
To connect to Confluent Cloud, enter the API Secret obtained from the Confluent Control Center.

Schema Registry Authentication



Use this field set to specify the Registry Username and Password in case the Schema Registry requires authentication. If you are using Avro data type, the Schema Registry URL and Schema Registry Authentication values must be provided as advised by the Confluent Control Center.

Registry Username or Key

 

Default Value: N/A
Example: transactions-key

String/Expression

Specify the username or key for schema registry authentication.

Registry Password or Secret

 

Default Value: N/A
Example: tr@nS@xt-001

String/Expression

Specify the password or secret for schema registry authentication.

 

 


See Also