Skip to content

Commit

Permalink
DCO Remediation Commit for lparadkar-rocket <lparadkar@rocketsoftware…
Browse files Browse the repository at this point in the history 
….com>

I, lparadkar-rocket <[email protected]>, hereby add my Signed-off-by to this commit: 41febb7

Signed-off-by: lparadkar-rocket <[email protected]>

DCO Remediation Commit for Pablo Carle <[email protected]>

I, Pablo Carle <[email protected]>, hereby add my Signed-off-by to this commit: 3f0d388

Signed-off-by: Pablo Carle <[email protected]>

DCO Remediation Commit for Sergei Kurnevich <[email protected]>

I, Sergei Kurnevich <[email protected]>, hereby add my Signed-off-by to this commit: 3b9ecfb

Signed-off-by: Sergei Kurnevich <[email protected]>

DCO Remediation Commit for ShobhaJayanna <[email protected]>

I, ShobhaJayanna <[email protected]>, hereby add my Signed-off-by to this commit: bf2f62f

Signed-off-by: ShobhaJayanna <[email protected]>

DCO Remediation Commit for Wen Ting Su (Sam) <[email protected]>

I, Wen Ting Su (Sam) <[email protected]>, hereby add my Signed-off-by to this commit: c2d5e23
I, Wen Ting Su (Sam) <[email protected]>, hereby add my Signed-off-by to this commit: 98a7386
I, Wen Ting Su (Sam) <[email protected]>, hereby add my Signed-off-by to this commit: 624fddc
I, Wen Ting Su (Sam) <[email protected]>, hereby add my Signed-off-by to this commit: b07fd2c
I, Wen Ting Su (Sam) <[email protected]>, hereby add my Signed-off-by to this commit: 277e136
I, Wen Ting Su (Sam) <[email protected]>, hereby add my Signed-off-by to this commit: 8d717f6

Signed-off-by: Wen Ting Su (Sam) <[email protected]>

Signed-off-by: Wen Ting Su (Sam) <[email protected]>
  • Loading branch information
@samanthasusu
samanthasusu committed Dec 4, 2023
1 parent 4d0592b commit 73d7919
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions docs/user-guide/certificate-configuration-scenarios.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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`.

Expand Down Expand Up @@ -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`.
Expand Down Expand Up @@ -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:
Expand Down Expand Up @@ -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:
Expand Down Expand Up @@ -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:
Expand Down

0 comments on commit 73d7919

Please sign in to comment.