Use the dsconfig command or the administrative console to synchronize changes to an Apache Kafka environment. You can reuse existing Ping Identity sync sources that were created for other Sync Pipes.
The following objects are required to configure a Kafka sync destination:
- Kafka cluster external server – Defines the procedure for connecting to a Kafka
cluster. The Kafka cluster external server can be referenced from multiple Kafka sync
destination configuration objects. The only required property is
bootstrap-server, which identifies some of the Kafka brokers in
When use-ssl is set to true, the following configuration changes are made:
trust-manager-provideris configured to validate the Kafka broker's SSL certificate.
key-manager-provideris configured to let the Kafka broker authenticate the PingDataSync Kafka producer.
- Kafka sync destination – References the Kafka cluster external server. The Kafka sync
destination must specify the name of the topic to use for publishing messages.
To adjust Kafka messages beyond the mapping, attribute filtering, and other configuration changes that PingDataSync makes, reference one or more of the KafkaSyncDestinationPlugin extension points that are implemented by using the Server SDK.
Run the prepare-endpoint-server command for the PingDirectory sync source.