kaldesai commented on code in PR #611:
URL: 
https://github.com/apache/incubator-kie-kogito-docs/pull/611#discussion_r1549717942


##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/add-custom-ca-to-a-workflow-pod.adoc:
##########
@@ -0,0 +1,191 @@
+= Adding a custom CA Certificate to a Container Running Java
+:compat-mode!:
+:keywords: kogito, sonataflow, workflow, serverless, operator, kubernetes, 
minikube, openshift, containers
+:keytool-docs: 
https://docs.oracle.com/en/java/javase/21/docs/specs/man/keytool.html
+
+If you're working with containers running Java applications and need to add a 
CA (Certificate Authority) certificate for secure communication, you can follow 
these steps. This guide assumes you are familiar with containers and have basic 
knowledge of working with YAML files.
+
+:toc:
+
+
+== Problem Space 
+
+If you have a containerized Java application that connects to an SSL endpoint 
with a certificate signed by an internal authority (like SSL terminated routes 
on a cluster) you need to make sure Java can read the CA Authority certificate 
and verify it. Java unfortunately doesn't load certificates directly, but 
rather store them in a {keytool-docs}[keystore].

Review Comment:
   ```suggestion
   If you have a containerized Java application that connects to an SSL 
endpoint with a certificate signed by an internal authority (like SSL 
terminated routes on a cluster), you need to make sure Java can read and verify 
the CA Authority certificate. Java unfortunately doesn't load certificates 
directly but rather stores them in a {keytool-docs}[keystore].
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to