Key pairs and certificates can be created for IOAGATE by using a SAF on the mainframe or an external CA, or with a combination of these two approaches. These keys and certificates can be used for communication with Control-M or Control-D. See the following table for the method appropriate to your site.
Table 173 Alternate methods of generating and signing IOAGATE keys and certificates
Keys generated by: |
CA |
See page |
---|---|---|
RACF |
RACF |
Using the basic methods - RACF or Control-M Configuration Manager |
Control-M Configuration Manager |
Control-M Configuration |
Using the basic methods - RACF or Control-M Configuration Manager |
RACF |
External CA |
|
outside mainframe |
Outside mainframe |
|
"Bring Your Own" (Control-M Configuration Manager) |
External CA |
Using the basic methods - RACF or Control-M Configuration Manager |
Table 174 Additional operations
To: |
See page |
---|---|
add keyring |
|
add client authentication |
Parent Topic |