Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Unable to overwrite runtime class for Kafka runtime connection

SA-72967

Summary



When configuring Kafka in  Pega with SASL mechanism of SCRAM-SHA-*, the user name and password are loaded using the Kafka.config file. The -D is loaded and added to Pega  JVM, and a module is created to expose the org.apache.kafka.common.security.scram.ScramLoginModule.Kafka authentication class. Finally, the Data-Admin-Kafka.validate must be overwritten such that it uses the client Java class. However, unable to overwrite the runtime class for Kafka runtime connection.


Error Messages



Error connecting to Kafka. Timeout expired while fetching topic metadata




Steps to Reproduce

  1. Set the SASL_SSL security profile and SCRAM-SHA-256 mechanism in the kafka_server_jaas configuration file.
  2. Set Pega's -D JAVA_OPTS argument with the file location.
  3. Test the Kafka rule.


Root Cause



This issue was determined to be a product enhancement request.
Pega does not support SCRAM-SHA* or overwrite the Kafka configuration.



Resolution



An enhancement request, FDBK-30087, is created for  consideration by Pega Product Management.

 
Suggest Edit

Published April 3, 2019 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us