Set Up Trust Between the Cloud Connector and Your On-Premise ABAP Systems (BW, BPC, or S/4HANA)
Configure your on-premise SAP ABAP system so that it trusts the Cloud Connector. This step is needed only if your live connection uses single sign-on.
- The Cloud Connector needs to trust the identity provider (IdP) that the customer uses (via syncing the IdPs in the Cloud Connector interface).
- The live system needs to trust the Cloud Connector (via the system certificate).
- The live system needs to be configured to accept a short-lived X.509 certificate that is forwarded by the Cloud Connector.
- The following steps are for uploading the certificate that you previously downloaded from the Cloud Connector (see related link) to an SAP BW or BPC on-premise system, and configuring the BW or BPC system to use principal propagation. For more information, see Configure Principal Propagation to an ABAP System for HTTPS.
Establish trust between the ABAP System and the Cloud Connector by importing the CA-issued
- Start SAP Logon.
- Log on to your on-premise ABAP system.
Open the Trust Manager.
You can type strust to find the Trust Manager.
- Double-click SSL server Standard.
- Switch to Edit mode.
- Select the Import certificate icon at the bottom of the screen.
- Choose the system certificate file that you previously downloaded from the Cloud Connector (not the sample certificate file).
Select Continue, and then select Allow to
grant access to the file.
The details of the certificate are displayed.
- Select Add to Certificate List.
- Verify that your system certificate appears in the Certificate List, and then save the configuration.
Configure the Internet Communication Manager (ICM).
The ICM ensures that communication between the SAP system and external sites via the HTTP, HTTPS, and SMTP protocols works properly. In its role as a server, the ICM processes requests from the Internet that arrive as URLs with the server/port combination that the ICM listens to. The ICM then calls the relevant local handler for the URL in question.
- Open the Edit Profiles screen (rz10).
- Select the DEFAULT profile.
- Select the Extended maintenance option.
- Select Change.
Select Parameter (create) and enter this
For the Parameter val field, enter the Issuer of the system certificate, which you can find in the Cloud Connector Administration application, on the Configuration screen, on the On Premise tab, in the System Certificate section.
Select the Back icon and save your
The new parameter appears in the parameter list.
Create a second parameter, which is the subject of the system
Select Parameter (create) and enter this Parameter name: icm/HTTPS/trust_client_with_subject.For the Parameter val field, enter the Subject DN of the system certificate, which you can also find in the System Certificate section.Note
The preceding steps describe how to configure one trusted proxy. If you want to configure multiple trusted proxies, use the parameter icm/trusted_reverse_proxy_0, which can be included in the profile multiple times, instead of the icm/HTTPS/trust_client_with_issuer and icm/HTTPS/trust_client_with_subject parameters. (Add the parameter multiple times using an incremented index at the end.)
For more information, and examples, see this SAP note: 2052899 .
- When both parameters appear in the parameter list, select the Back icon, and select Yes to update the profile.
- Save the profile, and select Yes to activate the profile.
- Select the Back icon to go back to the SAP Easy Access screen.
- Open the ICM Monitor (smicm).
- Select .
.The two new parameters are visible under HTTPS (SSL) settings.
Map the short-lived certificate.
You can do the mapping manually in the system, or make use of an identity management solution. For example, for large numbers of users, rule-based certificate mapping can save time and effort. The following steps describe the second option.
For detailed information, see Rule-based Mapping of Certificates.
- Open the Maintain Profile Parameters screen (rz11).
- In the Parameter Name field, type login/certificate_mapping_rulebased, and then select Display.
- Select Change Value.
- In the New Value field, type 1, and then save the change.
- Select the Back icon twice to go back to the SAP Easy Access screen.
- Open the Rule based Certificate Mapping - Display screen (certrule).
- Select Display/Change.
- Select .
- Choose the sample certificate file that you previously downloaded from the Cloud Connector (not the system certificate file).
- Select Open, and then select Allow to grant access to the file.
Select the Rule button to create a new rule.
For the Certificate Attr. field, select CN=<valid user identifier>. See Configure Your On-Premise Systems to Use the Cloud Connector for details.
For the Login As field, this setting depends on which attribute you configured in your identity provider as your user identifier. If you used a user name or email address, you can select those options from the drop-down list. If you chose any other attribute, select Alias from the list.
- Select Continue to create the rule.
- In the Rules list, double-click the check box in the Ext. Attributes or Attr column for the new rule, to open the Extended Attributes dialog.
- Select the check box Ignore case sensitivity in certificate entries, and select Continue.
- Verify that the rule has been added, and then save the change.
- Check that the user is mapped in the Certificate Status based on Persistence area.
Access ICF Services.
- In the ABAP system, choose transaction code SICF and go to Maintain Services.
- Select the GetServerInfo service.
- Double-click the service, and go to the Logon Data tab.
- Switch to Alternative Logon Procedure, and ensure that the Logon Through SSL Certificate logon procedure is listed before SAML LOGON.