/
Certificate file

Certificate file

Owned by proaxia
Feb 07, 2022
1 min read

Analogically to Message Broker running HTTPS service also SAP must present valid certificate together with its private key. And in this case also certificate can be generated and self-signed but of course those signed by trusted Root Authority are more reliable. Such certificate should be then imported using STRUST transaction unless there is one already.

Note: it is important that the certificate common name (issued to property in the example below) must match the service host name.

The usage of STRUST transaction is not within the scope of this guide

 

Related content

Test the SAP service in a web browser
Test the SAP service in a web browser
FSM Cloud Connector
More like this
Enable HTTPS service in SAP
Enable HTTPS service in SAP
FSM Cloud Connector
More like this
Enable use of HTTPS in the Message Broker's config
Enable use of HTTPS in the Message Broker's config
FSM Cloud Connector
More like this
Test the service in a web browser
Test the service in a web browser
FSM Cloud Connector
Read with this
Trust the certificate
Trust the certificate
FSM Cloud Connector
More like this
Incoming Service (FSM to SAP)
Incoming Service (FSM to SAP)
FSM Cloud Connector
Read with this

If you'd like to help us improve the documentation, please provide your feedback using the communication channels listed /wiki/spaces/PFCC/pages/1561427969. Learn about support possibilities here.