Administrator

Using SSL to Secure HTTPS Channel Communications in SAP Mobile Platform

Configure Secure Sockets Layer (SSL) and mutual SSL encryption for communication ports in SAP Mobile Platform.

Context

SAP Mobile Platform uses HTTPS to create a secure channel between:
  • The client (device) and SAP Mobile Platform Server
  • SAP Mobile Platform Server and the back end
In both of these scenarios, you can have one-way or mutual SSL.
SAP Mobile Platform uses the following HTTP and HTTPS ports, default assignments, and protocols.
Type Default Protocol Where Configured

Client communications, unsecured

8080

HTTP

File: <SMP_HOME>\Server\config_master\org.eclipse.gemini.web.tomcat\default-server.xml

Setting: <Connector port="8080" ...

Client communications with one-way SSL authentication

8081 (secure)

HTTPS

File: <SMP_HOME>\Server\config_master\org.eclipse.gemini.web.tomcat\default-server.xml

Setting: <Connector protocol="com.sap.mobile.platform.coyote.http11.SapHttp11Protocol" port="8081" ...

Client communications with mutual SSL authentication

8082 (secure)

HTTPS

File: <SMP_HOME>\Server\config_master\org.eclipse.gemini.web.tomcat\default-server.xml

Setting: <Connector protocol="com.sap.mobile.platform.coyote.http11.SapHttp11Protocol" port="8082" ...

Administration port, Management Cockpit and Kapsel command line interface (CLI) communications with one-way SSL authentication

8083 (secure)

HTTPS

File: <SMP_HOME>\Server\config_master\org.eclipse.gemini.web.tomcat\default-server.xml

Setting: <Connector protocol="com.sap.mobile.platform.coyote.http11.SapHttp11Protocol" port="8083" ...