Overview
KafkaTools provides the following functionality that allows publishing to and consuming from topics on Kafka Servers.
Smart Services
In order to process the messages consumed from Kafka, it is recommended to use the Transaction Manager application. The models designed to process messages will be configured an assigned through the transaction manager job types. See documentation for Transaction Manager
Key Features & Functionality
Please refer to the README for additional details.
Hi Sylvian/Team,
As you know, Kafka Plugin is one such Smart Service which allows the workflow to send a Kafka Message to a designated topic. This smart service is configured as one of the workflow steps based on the business requirement. Since this Smart Service is provided by Appian, the internal functioning of this Smart Service is abstracted by the consumers. The Smart Service in current form does not support retrieval of certificates from AWS Secrets Manager at runtime instead in expect the .JKS file to be provided at runtime which should be prestored in Appian internal document store.
Issue description: Currently we are exporting the application and pushing it to Bitbucket as part of our CICD application deployment. We have reviewed our code with client security team, They have found .jks file in the content of the application code and as per our industry best practices, we should not store any .jks files in bitbucket code.
1: Is there any alternate solution to not use .jks file?
2: Are there any other methods available to assure that the .jks files can be stored in the Appian Secured Document Center, but also not stored in the Bitbucket repository?
Appreciate your response.
Hi, as those JKS are in general not portable between environments, we use to keep them inside "XXX_Infra" applications that are exists on every environments, then use a constant of type Integer with values relative to the environment and use it when configuring the Smart Service. As this constant is Environment Specific treat it in your CI/CD the same way you already do with other customization files