/
Prepare certificate file

Prepare certificate file

Owned by proaxia
Last updated: Feb 04, 2022
1 min read

To enable HTTPS service, it is necessary to possess both private and public keys. In case, you do not possess a certificate signed by a trusted Root Authority, you can generate and use a self-signed certificate. Both, the private key and the public key wrapped in a certificate should be wrapped into a single file of type .pfx (certificate with a private key). 

 

Note: it is important that the certificate common name (issued to property in the example below) must match the service host name. In proaxia we use msgbroker.local for the host name (see sections below).

 

 

Related content

Import certificate to Windows Certificate Store
Import certificate to Windows Certificate Store
FSM Cloud Connector
More like this
Message Broker 4.X config example in YAML
Message Broker 4.X config example in YAML
FSM Cloud Connector
More like this
Set up the service client
Set up the service client
FSM Cloud Connector
More like this
Trust the certificate by client
Trust the certificate by client
FSM Cloud Connector
More like this
Enable HTTPS in the Message Broker's config
Enable HTTPS in the Message Broker's config
FSM Cloud Connector
More like this
Setting up secure (HTTPS) connection from SAP system to FSM Message Broker.
Setting up secure (HTTPS) connection from SAP system to FSM Message Broker.
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.