Secure communication between Unwired Server and any supported backend depends on the direction of the interaction between these components.
EIS to Unwired Server – can communicate only via the DCN feature. DCN uses HTTP or HTTPS and all requests are also authenticated via the DCN User role. If you enable HTTPS, you can enable mutual authentication between these components as required. To secure the channel:
The EIS developer uses HTTPS to construct and send DCN requests to the listener.
The administrator manages the certificates, then uses Sybase Control Center to configure an HTTPS listener for DCNs.
Unwired Server to EIS – Unwired Server can perform operation replays. The manner in which those replays are communicated depends on the EIS and whether or not the administrator secures this channel in Sybase Control Center:
REST/SOAP uses BASIC authorized over HTTP or HTTPS.
REST/SOAP for SAP uses BASIC/SSO2/X.509 authentication over HTTP or HTTPS.
JCo for SAP uses one of username/password, SSO2 tokens, or X.509 over SNC.
JDBC uses driver specific mechanisms to encrypt traffic. Review your JDBC driver documentation to learn how to configure this.