@AmitD17547706

Pega does not directly provide JAR files for the standard Kafka serializers you’ve listed because its Kafka integration uses its own internal serializer interfaces (PegaSerde, DataTransformSerde, and AvroSchemaRegistrySerde). These are tightly coupled with Pega’s data pages, data transforms, and schema registry integration, so they can’t be swapped out for external serializers without custom development. Pega doesn’t natively support the standard serializers like StringSerializer, JsonSerializer, or KafkaAvroSerializer out of the box for direct use in its Kafka connectors, but you can integrate them by building a custom Kafka serializer/deserializer class that implements Pega’s PegaSerde interface and internally delegates to one of the supported standard serializers from your list. This custom JAR can then be deployed into your Pega application’s classpath, and you can reference the custom serde in your Kafka data set or data flow configuration. In this way, you could plug in SecuPi’s supported serializers (e.g., StringSerializer or JsonSerializer) while still satisfying Pega’s serialization contract. The encryption/decryption logic from SecuPi would sit inside or wrap around these serializer calls, ensuring messages are encoded before sending and decoded after receiving. If your security team requires using only SecuPi-approved serializers, you’ll need to either implement this bridging layer yourself or engage Pega Professional Services to build it for you. Out of the box, there’s no toggle to switch from PegaSerde to standard serializers directly.