From 796abf3eda6a62781659a6d41918e2ced6ddd26a Mon Sep 17 00:00:00 2001 From: jyunmitch Date: Wed, 3 Aug 2022 14:21:03 -0500 Subject: [PATCH 1/3] ENDOC-535-ssl-note --- .../getting-started/openshift-install-by-operator.md | 8 ++++++++ .../getting-started/openshift-install-by-operator.md | 10 ++++++++++ 2 files changed, 18 insertions(+) diff --git a/vuepress/docs/next/tutorials/getting-started/openshift-install-by-operator.md b/vuepress/docs/next/tutorials/getting-started/openshift-install-by-operator.md index 815d890b5f..bd3a49d85f 100644 --- a/vuepress/docs/next/tutorials/getting-started/openshift-install-by-operator.md +++ b/vuepress/docs/next/tutorials/getting-started/openshift-install-by-operator.md @@ -140,6 +140,14 @@ Now let's create a new application similar to Scenario 3, but with the self-sign Once the deployment is complete, you can confirm that all routes use HTTPS with the self-signed certificate. You may still see security warnings in the browser. +#### Note: Multiple Certificate Chains +If you have multiple certificates to load into Openshift, you must pass each certificate with its own identifier. +```bash +ca0.crt: -\> a single ca certificate +ca1.crt: -\> another ca certificate +... +ca5.crt -\> last ca certificate +``` See the [Next Steps](#next-steps) below to continue your work with Entando. ## Next Steps diff --git a/vuepress/docs/v7.0/tutorials/getting-started/openshift-install-by-operator.md b/vuepress/docs/v7.0/tutorials/getting-started/openshift-install-by-operator.md index 815d890b5f..ffe37c6044 100644 --- a/vuepress/docs/v7.0/tutorials/getting-started/openshift-install-by-operator.md +++ b/vuepress/docs/v7.0/tutorials/getting-started/openshift-install-by-operator.md @@ -140,6 +140,16 @@ Now let's create a new application similar to Scenario 3, but with the self-sign Once the deployment is complete, you can confirm that all routes use HTTPS with the self-signed certificate. You may still see security warnings in the browser. +#### Note: Multiple Certificate Chains +If you have multiple certificates to load into Openshift, you must pass each certificate with its own identifier. +```bash +ca0.crt: -\> a single ca certificate +ca1.crt: -\> another ca certificate +... +ca5.crt -\> last ca certificate +``` + + See the [Next Steps](#next-steps) below to continue your work with Entando. ## Next Steps From 7e15298a8fd81e0a6aa2797ae839d5872526be46 Mon Sep 17 00:00:00 2001 From: jyunmitch Date: Wed, 3 Aug 2022 16:44:48 -0500 Subject: [PATCH 2/3] ENDOC-535-ssl-note review edit --- .../openshift-install-by-operator.md | 11 ++++++----- .../openshift-install-by-operator.md | 15 ++++++++------- 2 files changed, 14 insertions(+), 12 deletions(-) diff --git a/vuepress/docs/next/tutorials/getting-started/openshift-install-by-operator.md b/vuepress/docs/next/tutorials/getting-started/openshift-install-by-operator.md index bd3a49d85f..524c41fc11 100644 --- a/vuepress/docs/next/tutorials/getting-started/openshift-install-by-operator.md +++ b/vuepress/docs/next/tutorials/getting-started/openshift-install-by-operator.md @@ -117,6 +117,7 @@ type: kubernetes.io/tls Now create the `entando-ca-cert-secret` Secret, similar to what was done in Scenario 3, but this time using the self-signed certificate. 4. Go to `Workloads` → `Secrets` → `Create` and select `Key/value secret` + For multiple certificates, see note below on [Certificate Chains](#note-certificate-chains). 5. Set the `Secret Name`, e.g. `entando-ca-cert-secret` 6. Set the `Key`, e.g. `tls.crt` 7. Set the `Value` by clicking `Browse...` and loading the cert file from Step 1, e.g. `tls.crt` @@ -140,13 +141,13 @@ Now let's create a new application similar to Scenario 3, but with the self-sign Once the deployment is complete, you can confirm that all routes use HTTPS with the self-signed certificate. You may still see security warnings in the browser. -#### Note: Multiple Certificate Chains -If you have multiple certificates to load into Openshift, you must pass each certificate with its own identifier. +#### Note: Certificate Chains +If you have multiple certificates to load into OpenShift, you must pass each with its own identifier. ```bash -ca0.crt: -\> a single ca certificate -ca1.crt: -\> another ca certificate +ca0.crt: → a single CA certificate +ca1.crt: → another CA certificate ... -ca5.crt -\> last ca certificate +ca5.crt → last CA certificate ``` See the [Next Steps](#next-steps) below to continue your work with Entando. diff --git a/vuepress/docs/v7.0/tutorials/getting-started/openshift-install-by-operator.md b/vuepress/docs/v7.0/tutorials/getting-started/openshift-install-by-operator.md index ffe37c6044..c4b7a80a84 100644 --- a/vuepress/docs/v7.0/tutorials/getting-started/openshift-install-by-operator.md +++ b/vuepress/docs/v7.0/tutorials/getting-started/openshift-install-by-operator.md @@ -116,7 +116,9 @@ type: kubernetes.io/tls Now create the `entando-ca-cert-secret` Secret, similar to what was done in Scenario 3, but this time using the self-signed certificate. -4. Go to `Workloads` → `Secrets` → `Create` and select `Key/value secret` +4. Go to `Workloads` → `Secrets` → `Create` and select `Key/value secret`\ + For multiple certificates, see note below on [Certificate Chains](#note-certificate-chains). + 5. Set the `Secret Name`, e.g. `entando-ca-cert-secret` 6. Set the `Key`, e.g. `tls.crt` 7. Set the `Value` by clicking `Browse...` and loading the cert file from Step 1, e.g. `tls.crt` @@ -140,16 +142,15 @@ Now let's create a new application similar to Scenario 3, but with the self-sign Once the deployment is complete, you can confirm that all routes use HTTPS with the self-signed certificate. You may still see security warnings in the browser. -#### Note: Multiple Certificate Chains -If you have multiple certificates to load into Openshift, you must pass each certificate with its own identifier. +#### Note: Certificate Chains +If you have multiple certificates to load into OpenShift, you must pass each with its own identifier. ```bash -ca0.crt: -\> a single ca certificate -ca1.crt: -\> another ca certificate +ca0.crt: → a single CA certificate +ca1.crt: → another CA certificate ... -ca5.crt -\> last ca certificate +ca5.crt → last CA certificate ``` - See the [Next Steps](#next-steps) below to continue your work with Entando. ## Next Steps From c9a76a1f817c9471d43cd48541c94336d982be0b Mon Sep 17 00:00:00 2001 From: jyunmitch Date: Wed, 3 Aug 2022 16:50:41 -0500 Subject: [PATCH 3/3] ENDOC-535-ssl-note tiny edit --- .../tutorials/getting-started/openshift-install-by-operator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vuepress/docs/v7.0/tutorials/getting-started/openshift-install-by-operator.md b/vuepress/docs/v7.0/tutorials/getting-started/openshift-install-by-operator.md index c4b7a80a84..fcedfdf6c0 100644 --- a/vuepress/docs/v7.0/tutorials/getting-started/openshift-install-by-operator.md +++ b/vuepress/docs/v7.0/tutorials/getting-started/openshift-install-by-operator.md @@ -116,7 +116,7 @@ type: kubernetes.io/tls Now create the `entando-ca-cert-secret` Secret, similar to what was done in Scenario 3, but this time using the self-signed certificate. -4. Go to `Workloads` → `Secrets` → `Create` and select `Key/value secret`\ +4. Go to `Workloads` → `Secrets` → `Create` and select `Key/value secret` For multiple certificates, see note below on [Certificate Chains](#note-certificate-chains). 5. Set the `Secret Name`, e.g. `entando-ca-cert-secret`