To use a different trusted root file to validate the identity
of the trusted source, import that information to the remote node
record. IBM® Sterling Control
Center supports
Base 64-encoded key certificate files.
About this task
To create one or more trusted certificates, which are already loaded on your Sterling Connect:Direct® server:
Procedure
- Go to .
Note: If this option is disabled, it is likely due to the fact the server requires a secure
connection and one is not being used by IBM Sterling Control
Center.
- Choose the Server and Version.
Note: If you are unable to select the Server, it is likely due to the fact
that the connection to server is not secure or the server is down.
- Click Create New from the overflow menu icon (
) above the grid.
- Select one or more Sterling Connect:Direct servers or server groups on
which you want to import the certificates. Click Next.
- Take one of these steps:
- To identify all certificate information, select Enter Trusted Certificate
details.
- To import a certificate that exists on another server, select Start from an existing
Trusted Certificate on another server. Identify the server where the certificate is
located and the name of the certificate.
- Enter the required details and click Next.
- Identify when the certificate is to be imported:
- Click Submit. Now, to return to original page, click
Close. Else, click Configuration
Jobs to run the held job or view information about the completed job.