Handling Self-Signed Certificates

Remoting SDK's client channels of course support connecting to secure TLS/SSL Servers, simply by using the appropriate https://, superhttps://, tcps:// or supertcps:// URL scheme.

On most platforms, for this to work "out of the box", your server has to be set up with a "proper" certificate – that is, a certificate signed by (and usually bought from) a known certificate authority that is implicitly trusted by the operating system.

In order to safely and successfully connect to servers that use self-generated or self-signed certificates, some extra steps might be necessary. Options include manually installing the custom root certificate on the local OS (where feasible), or adding a few bits of extra code to the client to verify and authenticate the self-signed certificate.

Please refer to each platform's topic for more details: