Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In this article

Table of Contents
maxLevel2
absoluteUrltrue

Overview

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

Prerequisites

None.

Limitations

...

None.

and Known Issues

None.

Account Settings

Image Removed

...

Info
  • Asterisk ( * ): Indicates a mandatory field.

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

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

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

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

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

Field Name

Field Type

Description

Label*


Default Value: N/A
Example: Kafka SSL Account

String

Specify a unique label for the account.

N/A

Kafka SSL Account

Bootstrap Servers

Use this field set to configure a list of Bootstrap

servers. Click Image Removed to add a new row in this table for configuring bootstrap Bootstrap Server

servers. 

This field set contains the Bootstrap Server field.

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-

54

55-

234

334-

24

44-58.compute-1.amazonaws.com:

9092

8000

Schema Registry URL

String/Expression

Enter

Specify the schema registry server URL

.N/Ahttp://ec2-54-234-24-58.compute-1.amazonaws

.

com:8081Key 

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. 

Note
  • 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.

This field set contains the following fields:

  • Key
  • Value
Value
  • 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

Customer2

Example: 600

String/Expression/Integer

Specify the value for the corresponding key that

are Security Protocol

is not explicitly supported by the Snaps.

N/A600Truststore Filepath

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

SSLSASL_PLAINTEXTTruststore PasswordString

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

kafka.net.ssl.truststore

Example: test1234

String/Expression

Specify the password for the Truststore file.

N/A

test1234

Keystore Filepath

String/ExpressionSelect the location of Keystore filepath of the client.


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.


SSL Key Password

The keystore file contains the private key of the certificate; hence, it needs to be secure.

SSL Key Password


Default Value: N/A

d$ra0W$$#p!9

Example: password3

String/Expression

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

N/Apassword3

SASL Properties

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

This field set contains the following fields:

SASL Mechanism

  • SASL Username
  • SASL Password
  • 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

    PLAINSCRAM-SHA-512

    SASL Username or Key

    Default Value: N/A
    Example: Admin

    String/Expression

    Activates when you select SASL_SSL or SASL_PLAINTEXT for SecurityProtocol. 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.

    Image Removed

    SASL Password or SecretString
    Image Added

    SASL Password or Secret

    Default Value: N/A

    Admin

    Example: password4

    String/Expression

    Activates when you

    select 

    select SASL_SSL or SASL_PLAINTEXT

     for 

     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.

    N/Apassword4

    Schema Registry Authentication


    Use this field set to specify the Registry Username and Password in case the Schema Registry requires authentication.

     This field set contains the following fields:
    • Registry Username or Key
    • Registry Password or Secret

     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.

    Image Removed
    Image Added

    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

    transactions

    Example: tr@nS@xt-

    key

    001

    Registry Password or Secret

    String/Expression

    Specify the password or secret for schema registry authentication.

    N/Atr@nS@xt-001

    Insert excerpt
    Kafka Snap Pack
    Kafka Snap Pack
    nopaneltrue

    ...

    See Also