Blach hagajgienfeaihaepojeafoneafea
...
supports TLS/SSL handshaking for one-way authentication between a SAP CC client and SAP CC core server.
In one-way mode, only SAP CC Client validates the SAP CC Core Server to ensure that it receives data from the intended SAP CC Core Server. For implementing one-way mode, the SAP CC Core Server shares its Certificate(s) with the SAP CC Client.
To allow SAP CC agents to connect to the SAP CC Core Server with TLS enabled, you must:
Configure SAP CC Core Server with one-way authentication for the respective Instance and Services.
Configure Client to trust SAP CC Core Server.
Configure SAP CC Core Server
...
Before we can start configuring SAP CC Core Server, we need to know that SAP CC agents in MZ are connecting to the Dispatcher
instance through the TCP-IP layer:
...
SAP CC Architecture Diagram including SAP CM() as a third party element.
Info | |
---|---|
title | Info!For more information, please read Identifying services involved in the Client/Server communication |
For our case, you will turn on one-way for ExternalSecure
targeted service on the Dispatcher
instance.
Tip | ||
---|---|---|
Example!Example SAP CC Core Server Instance Map:
|
...
One of the example method is using the keytool
command to add this server certificate to client truststore, and use this truststore for your SAP CC agent.
Tip | |||
---|---|---|---|
title | Example!Import the server certificate “certificate.x509.pem“ to generate “client.truststore” file.
In the SAP CC agent, tick Enable Secured Connection checkbox and configure the following fields: Keystore Path: /path/to/client.truststore Keystore Password: examplepw |
Note |
---|
Note!SAP CC agent will only support a Keystore that is in PKCS#12 format. |
...