Keep in mind the following items before you copy CCIRTARM.
If you are using an HFS key database, CCIRTARM must be imported as a CA certificate within the SSL key database on the mainframe using the gskkyman utility.
If you are using a z/OS key database, CCIRTARM must be imported as a CA certificate to the z/OS key database using security software such as Top Secret, ACF2, or RACF.
Note: For more information about importing certificate keys and the gskkyman utility, see the IBM System SSL Programming Guide and Reference (SC24-5877).
When using CCISSLGW, CCIRTARM is used to authenticate certificates from remote hosts when the remote host initiates the connection, functioning as the client side of the SSL session. Although CCISSLGW and its remote hosts are ultimately peer-to-peer connections, the driver of the connection request determines their initial client/server identities for SSL session establishment. Since either the local or remote host can initiate the connection, either side could be the client end of the SSL session. Therefore, CCIRTARM is required to reside on all hosts that will connect over SSL.
If you have configured CCISSL to request and authenticate client certificates or you are running CCISSLGW, perform these steps:
Follow these steps:
If you are using a z/OS key database, consult your security software documentation or your security administrator for the import process.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|