Connector, http type
Connectors of the http type are used for receiving events over HTTP when working with Windows and Linux agents. Settings for a connector of the http type are described in the following tables.
Basic settings tab
Setting
|
Description
|
Name
|
Unique name of the resource. The maximum length of the name is 128 Unicode characters.
Required setting.
|
Tenant
|
The name of the tenant that owns the resource.
Required setting.
|
Type
|
Connector type: http.
Required setting.
|
Tags
|
Tags for resource search.
Optional setting.
|
URL
|
URL that you want to connect to. You can enter a URL in one of the following formats:
< host name >:< port number > < IPv4 address >:< port number > < IPv6 address >:< port number > :< port number >
Required setting.
|
Delimiter
|
The character that marks the boundary between events:
If you do not select a value in this drop-down list, \n is selected by default.
|
Description
|
Description of the resource. The maximum length of the description is 4000 Unicode characters.
|
Advanced settings tab
Setting
|
Description
|
Debug
|
The switch enables resource logging. The toggle switch is turned off by default.
|
Character encoding
|
Character encoding. The default is UTF-8.
|
TLS mode
|
TLS encryption mode. When using TLS encryption, you cannot specify an IP address in the URL field on the Basic settings tab. Available values:
- Disabled means TLS encryption is not used. This value is selected by default.
- Enabled means TLS encryption is used, but certificates are not verified.
- With verification means TLS encryption is used with verification of the certificate signed with the KUMA root certificate. The root certificate and key of KUMA are created automatically during application installation and are stored on the KUMA Core server in the /opt/kaspersky/kuma/core/certificates/ directory.
Obsolete encryption mode, deprecated. Will be removed in future versions of KUMA. - Custom PFX means TLS encryption with a PFX secret. You must generate a PFX certificate with a private key in PKCS#12 container format, then upload the PFX certificate to the KUMA web interface as a PFX secret. If you select this value, in the PFX secret drop-down list, specify a PFX secret with a certificate signed by a certification authority. You can select an existing PFX secret or create a new PFX secret. To create a new PFX secret, select Create new.
If you want to edit the settings of an existing secret, click the pencil icon next to it. How to create a PFX secret? To create a PFX secret:
- In the Name field, enter the name of the PFX secret.
- Click Upload PFX and select the PKCS#12 container file to which you exported the PFX certificate with the private key.
- In the Password field, enter the PFX certificate security password that was set in the PFX Certificate Export Wizard.
- Click the Create button.
The PFX secret is created and displayed in the PFX secret drop-down list.
- Custom PFX with client authentication means TLS encryption with a PFX secret. In this mode, the client is authenticated using a certificate.
You must generate a PFX certificate with a private key in PKCS#12 container format, then upload the PFX certificate to the KUMA web interface as a PFX secret. If you select this value, in the PFX secret drop-down list, specify a PFX secret with a certificate signed by a certification authority. You can select an existing PFX secret or create a new PFX secret. To create a new PFX secret, select Create new. If you want to edit the settings of an existing secret, click the pencil icon next to it. How to create a PFX secret? To create a PFX secret:
- In the Name field, enter the name of the PFX secret.
- Click Upload PFX and select the PKCS#12 container file to which you exported the PFX certificate with the private key.
- In the Password field, enter the PFX certificate security password that was set in the PFX Certificate Export Wizard.
- Click the Create button.
The PFX secret is created and displayed in the PFX secret drop-down list.
|
Page top
[Topic 220745]