Kafka Connection

The Kafka Connection module allows users to configure and manage connections to external Kafka brokers. These connections are used to publish data from Infraon workflows to Kafka topics.

This module serves as the foundation for Kafka-based integrations, enabling workflow events to trigger real-time data publishing to external systems.

What you see on the screen

• List of configured Kafka connections

• Columns:

  • Name – Identifier of the Kafka connection

  • Bootstrap Servers – Kafka broker endpoint(s)

  • Security Protocol – Connection type (e.g., SASL, SSL)

  • Status – Active / Inactive

  • Creation Time – Timestamp of creation

  • Action – Edit / Delete options

• Add the Kafka Connection button to create a new connection

How does it work

1. A Kafka connection is created by providing:

• Broker details (Bootstrap Servers)

• Security configuration (SSL, SASL, etc.)

• Authentication credentials (if required)

1. The connection can be:

• Tested to verify connectivity

• Activated or deactivated

1. Once active, the connection becomes available in the Workflow module.

2. In workflows:

• A Kafka Integration action is added

• The user selects the Kafka connection

• Available topics are fetched dynamically

1. When the workflow is executed:

• Data is published to the selected Kafka topic(s)

• External systems consume this data

1. System tracks:

• Success or failure of message publishing

• Logs in workflow execution and recent activities

• Only active Kafka connections are available for workflow usage

• Supports multiple security protocols (SSL, SASL, etc.)

• Enables event-driven data publishing from workflows

• Provides audit logs for connection changes

• Ensures validation and error handling during execution

Add Kafka Connection

• To create a new Kafka connection, click Add Kafka Connection located at the top right corner of the page.

• This opens the Add Kafka Connection panel, where you can configure broker details, security settings, and authentication required to establish communication with the Kafka cluster.

Configuration Details | Kafka Connection

Label	Action	Description / Example
Connection Name *	Enter value	Specify a unique and identifiable name for the Kafka connection. Example: Ticket_Event_Stream, Production_Kafka
Brokers *	Enter value	Enter the Kafka broker endpoint(s) in “host: port” format. These brokers act as entry points to the Kafka cluster and are used to establish the connection. Multiple brokers can be provided (comma-separated) to ensure high availability and fault tolerance. Example: 192.168.1.10:9092, kafka-prod:9092
Status	Toggle on/off	Enables or disables the Kafka connection. When enabled (Active), the connection becomes available for selection in workflow actions. When disabled (Inactive), it is hidden from workflow configuration but remains saved in the system.
Security Type *	Select option	Defines the communication protocol and authentication mechanism used to connect with the Kafka cluster. This selection dynamically controls which additional fields are required (such as credentials or certificates). Available options include: None Plaintext SASL (Plaintext) SSL SASL (SSL)

The fields displayed in the configuration form change dynamically based on the selected Security Type. This ensures that only relevant authentication details are required.

Field Behavior | Security Type

Security Type	Additional Fields	Description
None	None	No authentication or encryption is applied. The connection is established without any security layer. Suitable only for trusted internal environments without enforced security.
Plaintext	None	Similar to “None”, but explicitly indicates communication over an unencrypted channel. Data is transmitted as plain text without encryption or authentication.
SSL	Certificate	Enables encrypted communication between Infraon and Kafka using SSL/TLS. A valid certificate key must be provided to establish a secure connection. No username/password authentication is required.
SASL (Plaintext)	Username, Password	Enables SASL-based authentication without encryption. Credentials are required to authenticate with the Kafka broker, but communication is not encrypted.
SASL (SSL)	Username, Password, Certificate	Provides both authentication and encryption. Requires valid credentials (username/password) along with an SSL certificate. This is the most secure option and recommended for production environments.

• Click Test to validate the Kafka connection using the provided configuration details. The system attempts to establish a connection with the Kafka broker and verifies credentials, security settings, and network accessibility.

On success: A confirmation message is displayed

On failure: An error message is shown with details for troubleshooting

• Click Save to store the Kafka connection configuration. Once saved:

  • The connection becomes available in workflow actions (if marked Active)

  • It can be selected in the Kafka Integration workflow card

  • Configuration changes are tracked in audit logs

• It is recommended to Test the connection before saving

• Only Active connections are available in the workflow configuration

• Internal Kafka topics (e.g., consumer_offsets) are automatically excluded

• All create, update, and delete actions are recorded in Audit Logs