Zowe is able to work with certificates held in a z/OS Keyring. For background on Zowe certificates, see Configuring Zowe certificates. To configure Zowe certificates in a key ring, run the
ZWEKRING JCL that contains the security commands to create the key ring and manage the certificates that Zowe will use. The
ZWEKRING JCL is provided as part of the PDS sample library
SZWESAMP that is delivered with Zowe.
Before you submit the JCL, you must customize it and review it with a system programmer who is familiar with z/OS certificates and key rings. The JCL member contains commands for three z/OS security managers: RACF, TopSecret, and ACF/2.
ZWEKRING JCL contains commands for the following scenarios:
- Creation of a local CA which is used to sign a locally generated certificate, both of which are placed into the key ring.
- (Beta) Importing an existing certificate already held in z/OS to the key ring for use by Zowe.
- (Beta) Creation of a locally generated certificated and signing it with an existing certificate authority, and placing the certificate into the key ring.
Note: The scenarios marked Beta are provided for technical preview. If you have any feedback on using key rings, create an issue in the Zowe community repo at https://github.com/zowe/community.
After you run the
ZWEKRING JCL, a key ring that contains the Zowe certificate is created. In order for a Zowe instance to work with the keystore certificate, you also need to create a USS keystore directory. This USS keystore directory does not contain any certificates, but is required for the Zowe instance.env file to configure the Zowe shell correctly so that the keystore certificate can be located by the Zowe runtime.
To create the USS keystore directory after successfully running
ZWEKRING JCL member, run the script
<RUNTIME_DIR>/bin/zowe-setup-certificates.sh. This script has an input parameter
-p which specifies the location of a configuration file controlling how and where the directory and its contents are created. Copy the file
<RUNTIME_DIR>/bin/zowe-setup-certificates.env to a writeable location and review and edit its contents to match property values used in
ZWEKRING JCL member. Then, run the script by using the following command:
To customize the
ZWEKRING JCL, edit the JCL variables at the beginning of the JCL and carefully review and edit all the security commands that are valid for your security manager. Review the information in this section when you customize the JCL.
PRODUCT variable specifies the z/OS security manager. The default value is
RACF. Change the value to
TSS if you are using Access Control Facility CA-ACF2 or CA Top Secret for z/OS as your z/OS security manager.
The Zowe certificate is used on the northbound edge of the API Mediation Layer to encrypt data between web browser and other client applications such as the Zowe command line interface. These client applications will validate that the network TCP/IP address that they have accessed the encrypted data from matches the network address in the certificate. If the address does not match, the browser will not continue as it will consider the site as unsecure.
To ensure that the browser is able to establish a secure connection, set the
IPADDRESS in the
ZWEKRING JCL member to match the hostname and TCP/IP address of the Zowe API Mediation Layer.
ZOWERING label is used for the name of the key ring created. The default value is
LABEL label specifies the certificate name and defaults to
- The value of the
ZOWERINGlabel should match the value of the
ZOWE_KEYRINGvariable in the
- The value of the
LABELlabel should match the value of the
KEYSTORE_ALIASvariable in the
ROOTZFCA label connects the root CA of the z/OSMF certificate with the Zowe key ring.
When to set this label?
The value of the parameter
VERIFY_CERTIFICATES in the
zowe-certificates.env file in the
KEYSTORE_DIRECTORY controls whether Zowe's servers validate the authenticity of any southbound certificates at runtime. If the value is
true, then the certificate must be signed by a recognized certificate authority (CA), and if the value is
false then self-signed certificates are allowed. This section of the keystore configuration is only required if you are using
When you set
VERIFY_CERTIFICATES=true, then Zowe will validate the authenticity of the z/OSMF certificate, so the root CA of the z/OSMF certificate must be connected with the Zowe key ring. You can connect them by setting the label
If you are unsure of the root CA you can find it by listing the chain of the z/OSMF certificate using the following commands:
- RACF RACDCERT ID(IZUSVR) LISTCHAIN(LABEL('DefaultzOSMFCert.IZUDFLT'))
- Top Secret TSS LIST(IZUSVR) LABLCERT('DefaultzOSMFCert.IZUDFLT') CHAIN
- ACF2 SET PROFILE(USER) DIVISION(CERTDATA)CHKCERT IZUSVR LABEL(DefaultzOSMFCert.IZUDFLT) CHAIN
ZWEKRING JCL runs successfully, it will create a key ring named
ZoweKeyring owned by
ZWESVUSR containing the following:
- The Zowe certificate (called
- The local CA (called
- The certificate used to encrypt the JSON Web Token (JWT) required for single sign-on (called
zowe-setup-certificates.sh script executes successfully, it will generate the USS
KEYSTORE_DIRECTORY that contains the file
zowe-certificates.env. This file is used in the Zowe instance configuration step. See Creating and configuring the Zowe instance directory.
The JCL member
ZWENOKYR provided in the PDS sample library
SZWESAMP contains the inverse commands contained in
ZWEKKRING. This allows an environment to be cleaned up and have one or more certificates, key rings, and certificate authorities created by
ZWEKRING removed from the z/OS environment. This is useful if you are creating a DevOps pipeline to install and configure and environment for Zowe using
ZWEKRING and want to clean that environment before rerunning the pipeline.