Configuring TLS connections between the Data Streamer and its subscribers
To secure communications between the Z Common Data Provider Data Streamer and its subscribers, you must choose a streaming protocol that supports Transport Layer Security (TLS) when you configure a subscriber in a policy. You must also configure the Data Streamer and its subscribers to use TLS.
Before you begin

Subscribers | Protocols |
---|---|
Splunk | Splunk via Data Receiver secure |
Splunk HEC secure | |
Splunk HEC with customized field support secure | |
Logstash | Logstash secure |
Fluentd | Fluentd secure |
Humio | Humio via HTTP secure |
Db2® | Enterprise Data Warehouse (DB2®) secure |
Generic HTTPS subscriber | Generic HTTP secure |
For more information about the streaming protocols, see Subscriber configuration. The streaming protocols that support TLS contain secure in the name except for Apache Kafka subscribers.
For Apache Kafka subscribers, whether to enable secure communications between the Data Streamer
and Apache Kafka is not controlled by the protocol you select. Instead, specify the file path of the
Apache Kafka producer or consumer properties file in the policy and set
security.protocol=SSL
or SASL_SSL
in these files. The streaming
protocol for Apache Kafka subscribers, with or without secure communication enabled, is
CDP Kafka.
About this task
TLS is a standard technology used for enabling secure communications between client and server to ensure data security and integrity. The following sections explain how to configure TLS on the Data Streamer and its subscriber respectively.