> 12.1 | Secure Data Transfer

> This feature makes it possible for MIDlets to use safe data links to external communications partners. The specification IMP-NG defines two java classes with this characteristic - HTTPS-Connection and SecureConnection
> .
> The Siemens implementation follows the recommendations in IMP-NG:
> HTTPSConnection

> • | HTTP over TLS as documented in RFC 2818 and TLS Protocol Version 1.0 as specified in RFC 2246.

> SecureConnection

> • | TLS Protocol Version 1.0 as specified in RFC 2246

> Two modes exist for safe data links.
> Mode 1:

> • | No examination of the server certificate takes place when setting up the connection. The authenticity of the server certificate is not verified. See Figure 59.

> Figure 59: Mode 1 – Customer Root Certificate does not exist
> Mode 2 (see Section 12.2.1, 1. Step):

> • | Customer Root Certificate is inside of the module.

> • | Command: Switch on Certificate Verification for HTTPS Connections was sent.

> • | The server certificate is examined when setting up a connection. Two configurations are valid. The server certificate is identical to the certificate in the module (both certificates are self signed root certificates) or the server certificate forms a chain with the certificate of the module. Thus the authenticity of the server certificate can be examined with the help of the certificate of the module. See Figure 60 and Figure 61.

> Figure 60: Mode 2 - Server Certificate and Certificate into module are identical
> Figure 61: Mode 2 - Server Certificate and self signed root Certificate in module form a chain