Many applications require JKS files to enable TLS (Transport Layer Security). In case you are not sure what a JKS file is, you can read about what a JKS file is and see how to make a self-signed one right here.
Converting a CA Certificate to a JKS File
To convert the files a CA provides you into a JKS file you can do the following, which is lightly modified from this other article I followed.
cat /etc/ssl/certs/ca-bundle.crt IntermediateCA.crt > ca-certs.pem openssl pkcs12 -export -in ssl_certificate.crt -inkey app.key -chain -CAfile ca-certs.pem -name "*.app.company.com" -out app.p12 keytool -importkeystore -deststorepass Password123! -destkeystore app.jks -srckeystore app.p12 -srcstoretype PKCS12
Note that the domain must match the one specified in the certificate. Assuming these 3 commands work, you should have a proper JKS file when done.
Given the certificate is from a CA, clients should not need a copy of the JKS file to talk to servers that are using it. For example, if my Presto server uses this JKS file, JDBC clients on other hosts can talk to it over SSL even though they do not have a copy of the file themselves.
NOTE: The JKS file will only work properly when used against the correct domain. E.g. if you have a load balancer at https://load-balancer.app2.company.com pointing at your server running your JKS file which is for https://server1.app.company.com, it will not work. You have to make a CNAME so your load balancer actually looks like it is also under app.company.com (what’s in the cert) and not app2.company.com.