APAR status
Closed as duplicate of another APAR.
Error description
Add support for enabling two-way TLS between ZAPM components that are communicating using the internal Kafka service network. Users Affected: Any zAPM Connect users deploying in a production cluster environment that want to secure communication between ZAPM components within the cluster. Problem Description: By default Kafka does not use encryption when transmitting data over its internal broker network. Data could be intercept and read. Solution: By enabling two-way TLS for Kafka's internal communication the Kafka broker will both authenticate users and encrypt the data it is transmitting. This ensures only authenticated users (ZAPM components) can read transmitted data. Please refer to the product documentation for instructions on how to enable two-way TLS. This APAR is resolved with OA66309/UJ95179
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
This APAR is resolved with OA66309/UJ95179
APAR Information
APAR number
OA66310
Reported component name
Z APM CONNECT
Reported component ID
5698ABF00
Reported release
610
Status
CLOSED DUB
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2024-03-25
Closed date
2024-04-29
Last modified date
2024-04-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCL4Q","label":"IBM Z Application Performance Management Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"610","Line of Business":{"code":"LOB70","label":"Z TPS"}}]
Document Information
Modified date:
30 April 2024