Kafka type

When creating this type of connector, you need to define values for the following settings:

Basic settings tab:

Name (required)—a unique name for this type of resource. Must contain 1 to 128 Unicode characters.
Tenant (required)—name of the tenant that owns the resource.
Type (required)—connector type, kafka.
URL—URL that you need to connect to. Available formats: hostname:port, IPv4:port, IPv6:port.
Topic—subject of Kafka messages. Must contain from 1 to 255 of the following characters: a–z, A–Z, 0–9, ".", "_", "-".
Authorization—requirement for Agents to complete authorization when connecting to the connector:
- disabled (by default).
- PFX.
  When this option is selected, a certificate must be generated with a private key in PKCS#12 container format in an external Certificate Authority. Then the certificate must be exported from the key store and uploaded to the KUMA web interface as a PFX secret.
  
  Add PFX secret
  1. If you previously uploaded a PFX certificate, select it from the Secret drop-down list.
    If no certificate was previously added, the drop-down list shows No data.
  2. If you want to add a new certificate, click the button on the right of the Secret list.
    The Secret window opens.
  3. In the Name field, enter the name that will be used to display the secret in the list of available secrets.
  4. Click the Upload PFX button to select the file containing your previously exported certificate with a private key in PKCS#12 container format.
  5. In the Password field, enter the certificate security password that was set in the Certificate Export Wizard.
  6. Click the Save button.
  The certificate will be added and displayed in the Secret list.
- plain.
  If this option is selected, you must indicate the secret containing user account credentials for authorization when connecting to the connector.
  
  Add secret
  1. If you previously created a secret, select it from the Secret drop-down list.
    If no secret was previously added, the drop-down list shows No data.
  2. If you want to add a new secret, click the button on the right of the Secret list.
    The Secret window opens.
  3. In the Name field, enter the name that will be used to display the secret in the list of available secrets.
  4. In the User and Password fields, enter the credentials of the user account that the Agent will use to connect to the connector.
  5. If necessary, add any other information about the secret in the Description field.
  6. Click the Save button.
  The secret will be added and displayed in the Secret list.
GroupID—the GroupID parameter for Kafka messages. Must contain from 1 to 255 of the following characters: a–z, A–Z, 0–9, ".", "_", "-".
Description—resource description: up to 4,000 Unicode characters.

Advanced settings tab:

Size of message to fetch—should be specified in bytes. The default value is 16 MB.
Maximum fetch wait time—timeout for a message of the defined size. The default value is 5 seconds.
Character encoding setting specifies character encoding. The default value is UTF-8.
TLS mode specifies whether TLS encryption is used:
- Disabled (default)—do not use TLS encryption.
- Enabled—use encryption without certificate verification.
- With verification—use encryption with verification that the certificate was signed with the KUMA root certificate. The root certificate and key of KUMA are created automatically during program installation and are stored on the KUMA Core server in the folder /opt/kaspersky/kuma/core/certificates/.
- Custom CA—use encryption with verification that the certificate was signed by a Certificate Authority. The secret containing the certificate is selected from the Custom CA drop-down list, which is displayed when this option is selected.
  Creating a certificate signed by a Certificate Authority
  To use this TLS mode, you must do the following on the KUMA Core server (OpenSSL commands are used in the examples below):
  1. Create the key that will be used by the Certificate Authority.
    Example command:
    
    openssl genrsa -out ca.key 2048
  2. Generate a certificate for the key that was just created.
    Example command:
    
    openssl req -new -x509 -days 365 -key ca.key -subj "/CN=<common host name of Certificate Authority>" -out ca.crt
  3. Create a private key and a request to have it signed by the Certificate Authority.
    Example command:
    
    openssl req -newkey rsa:2048 -nodes -keyout server.key -subj "/CN=<common host name of KUMA server>" -out server.csr
  4. Create a certificate signed by the Certificate Authority. The subjectAltName must include the domain names or IP addresses of the server for which the certificate is being created.
    Example command:
    
    openssl x509 -req -extfile <(printf "subjectAltName=DNS:domain1.ru,DNS:domain2.com,IP:192.168.0.1") -days 365 -in server.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out server.crt
  5. The obtained server.crt certificate should be uploaded in the KUMA web interface as a certificate-type secret, which should then be selected from the Custom CA drop-down list.
  When using TLS, it is impossible to specify an IP address as a URL.
  
  To use KUMA certificates on third-party devices, you must change the certificate file extension from CERT to CRT. Otherwise, error x509: certificate signed by unknown authority may be returned.
Debug—a toggle switch that lets you specify whether resource logging must be enabled. By default, this toggle switch is in the Disabled position.

Page top