From 825706c63e1aea2dfb823ec9b110c4f5de24db2c Mon Sep 17 00:00:00 2001 From: Maxim Svistunov Date: Wed, 18 Jun 2025 14:25:37 +0200 Subject: [PATCH] Custom SSL certificate process for Capsules clarification --- .../modules/proc_creating-a-custom-ssl-certificate.adoc | 5 +++-- ...oying-a-custom-ssl-certificate-to-smart-proxy-server.adoc | 5 +++++ 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/guides/common/modules/proc_creating-a-custom-ssl-certificate.adoc b/guides/common/modules/proc_creating-a-custom-ssl-certificate.adoc index 2e2f47edfb6..a329756bdb1 100644 --- a/guides/common/modules/proc_creating-a-custom-ssl-certificate.adoc +++ b/guides/common/modules/proc_creating-a-custom-ssl-certificate.adoc @@ -7,8 +7,9 @@ If you already have a custom SSL certificate for {ProductName}, skip this proced endif::[] ifeval::["{context}" == "{smart-proxy-context}"] -On {ProjectServer}, create a custom certificate for your {ProductName}. -If you already have a custom SSL certificate for {ProductName}, skip this procedure. +On {ProjectServer}, you must generate a unique private key and Certificate Signing Request (CSR) for each {ProductName} that you want to secure with a custom SSL certificate. + +Use this procedure for each {ProductName} that requires a custom SSL certificate. endif::[] ifdef::load-balancing[] diff --git a/guides/common/modules/proc_deploying-a-custom-ssl-certificate-to-smart-proxy-server.adoc b/guides/common/modules/proc_deploying-a-custom-ssl-certificate-to-smart-proxy-server.adoc index 4cb95e8e4e8..88fcfa0f1d1 100644 --- a/guides/common/modules/proc_deploying-a-custom-ssl-certificate-to-smart-proxy-server.adoc +++ b/guides/common/modules/proc_deploying-a-custom-ssl-certificate-to-smart-proxy-server.adoc @@ -13,6 +13,11 @@ For more information, see xref:Registering_Proxy_to_Server_{smart-proxy-context} * {SmartProxyServer} packages are installed. For more information, see xref:Installing_Proxy_Packages_{smart-proxy-context}[]. +[NOTE] +==== +Once you have obtained the server certificate, private key, and CA chain from the Certificate Authority (CA) for each {SmartProxyServer}, organize these files into separate directories named after each {SmartProxyServer} on your {ProjectServer}. +==== + .Procedure . On your {ProjectServer}, generate a certificate bundle: +