From 73d7919568f364bf36ac9fd5e58da0a0fa02acc6 Mon Sep 17 00:00:00 2001 From: "Wen Ting Su (Sam)" Date: Mon, 4 Dec 2023 22:34:27 +0800 Subject: [PATCH] DCO Remediation Commit for lparadkar-rocket I, lparadkar-rocket , hereby add my Signed-off-by to this commit: 41febb79fe07ae4670a746301b7215740e65a3c7 Signed-off-by: lparadkar-rocket DCO Remediation Commit for Pablo Carle I, Pablo Carle , hereby add my Signed-off-by to this commit: 3f0d3888423905a60aa72bc0e4ee8be31ce7834e Signed-off-by: Pablo Carle DCO Remediation Commit for Sergei Kurnevich <61471197+skurnevich@users.noreply.github.com> I, Sergei Kurnevich <61471197+skurnevich@users.noreply.github.com>, hereby add my Signed-off-by to this commit: 3b9ecfb727b8b0081cea8a3a395d278c1c26de42 Signed-off-by: Sergei Kurnevich <61471197+skurnevich@users.noreply.github.com> DCO Remediation Commit for ShobhaJayanna <36433611+Shobhajayanna@users.noreply.github.com> I, ShobhaJayanna <36433611+Shobhajayanna@users.noreply.github.com>, hereby add my Signed-off-by to this commit: bf2f62fbaa721b7db179d9e7477ddc75e7184691 Signed-off-by: ShobhaJayanna <36433611+Shobhajayanna@users.noreply.github.com> DCO Remediation Commit for Wen Ting Su (Sam) I, Wen Ting Su (Sam) , hereby add my Signed-off-by to this commit: c2d5e239df7013223e5f52f1b8ac41a345891967 I, Wen Ting Su (Sam) , hereby add my Signed-off-by to this commit: 98a73862bbf28cea7ba227a4482030437729c228 I, Wen Ting Su (Sam) , hereby add my Signed-off-by to this commit: 624fddc413f15bd35acfda827ff6dc16fb75ece9 I, Wen Ting Su (Sam) , hereby add my Signed-off-by to this commit: b07fd2c678379338bf03a691eef2c1588176c679 I, Wen Ting Su (Sam) , hereby add my Signed-off-by to this commit: 277e136947f50d0703cd7e033fb07de17db35769 I, Wen Ting Su (Sam) , hereby add my Signed-off-by to this commit: 8d717f60557b4eae4364ed9c973ae735dae2cb72 Signed-off-by: Wen Ting Su (Sam) Signed-off-by: Wen Ting Su (Sam) --- docs/user-guide/certificate-configuration-scenarios.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/user-guide/certificate-configuration-scenarios.md b/docs/user-guide/certificate-configuration-scenarios.md index fb01752fe0..9f7a8da801 100644 --- a/docs/user-guide/certificate-configuration-scenarios.md +++ b/docs/user-guide/certificate-configuration-scenarios.md @@ -56,7 +56,7 @@ Ensure that all alias values for all scenarios use only lower-case. ## Scenario 1: Use a file-based (PKCS12) keystore with Zowe generated certificates -Use the following procedure to configure the `zowe.setup` section in your yaml file to enable Zowe to use generated PKCS12 certificates to be used with a keystore directory to store your certificates. +Use the following procedure to configure the `zowe.setup.certificate` section in your yaml file to enable Zowe to use generated PKCS12 certificates to be used with a keystore directory to store your certificates. 1. Set the `type` of the certificate storage to `PKCS12`. @@ -133,7 +133,7 @@ Check out the [video tutorials](https://www.youtube.com/playlist?list=PL8REpLGaY ## Scenario 2: Use a file-based (PKCS12) keystore and import a certificate generated by another CA -Use the following procedure to configure the `zowe.setup` section in your yaml file to enable Zowe to use a file-based PKCS12 keystore to import a certificate generted by another CA. +Use the following procedure to configure the `zowe.setup.certificate` section in your yaml file to enable Zowe to use a file-based PKCS12 keystore to import a certificate generted by another CA. 1. Set the `type` of the certificate storage to `PKCS12`. @@ -191,7 +191,7 @@ PEM format certificate authorities can be imported and trusted. ``` Your yaml file is now configured to enable Zowe to use a file-based PKCS12 keystore to import a certificate generted by another CA. ## Scenario 3: Use a z/OS keyring-based keystore with Zowe generated certificates -Use the following procedure to configure the `zowe.setup` section in your yaml file to enable Zowe to use a z/OS keyring-based keystore with Zowe generated certificates. +Use the following procedure to configure the `zowe.setup.certificate` section in your yaml file to enable Zowe to use a z/OS keyring-based keystore with Zowe generated certificates. 1. Set the `type` of the certificate storage to one of the following keyring types: @@ -269,7 +269,7 @@ Due to the limitation of the `RACDCERT` command, this field should contain exact Your yaml file is now configured to enable Zowe to use a z/OS keyring-based keystore with Zowe generated certificates. ## Scenario 4: Use a z/OS keyring-based keystore and connect to an existing certificate -Use the following procedure to configure the `zowe.setup` section in your yaml file to use a z/OS keyring-based keystore and connect to an existing certificate. +Use the following procedure to configure the `zowe.setup.certificate` section in your yaml file to use a z/OS keyring-based keystore and connect to an existing certificate. 1. Set the `type` of the certificate storage to one of the following keyring types: @@ -329,7 +329,7 @@ If you would like to use this example in your Zowe configuration YAML file, repl Your yaml file is now configured to use a z/OS keyring-based keystore and connect to an existing certificate. ## Scenario 5: Use a z/OS keyring-based keystore and import a certificate stored in a data set -Use the following procedure to configure the `zowe.setup` section in your yaml file to use a z/OS keyring-based keystore and import a certificate stored in a data set. +Use the following procedure to configure the `zowe.setup.certificate` section in your yaml file to use a z/OS keyring-based keystore and import a certificate stored in a data set. 1. Set the `type` of the certificate storage to one of the following keyring types: