trusted_certificates=filename

• TLS, HTTPS

None

When synchronization occurs through a TLS synchronization stream, the MobiLink server sends its certificate to the client, and the certificate of the entity that signed it, and so on up to a self-signed root.

The client checks that the chain is valid and that it trusts the root certificate in the chain. This feature allows you to specify which root certificates to trust.

Certificates are used according to the following rules of precedence:

You cannot use both the trusted_certificates option and the trusted_certificate_name option in the same set of stream options.

For information about how to set network protocol options with dbmlsync, see CommunicationAddress (adr) extended option.

For information about how to set network protocol options with UltraLite, see UltraLite network protocol options.

• trusted_certificate_name
• UltraLite file path formats in connection parameters
• MobiLink client/server communications encryption
• -x mlsrv16 option
• certificate_company
• certificate_name
• certificate_unit

The following example sets up RSA encryption for an HTTPS protocol. This requires setup on the server and client. Each command must be written on one line.

The server implementation is:

mlsrv16 
   -c "DSN=SQL Anywhere 16 Demo;UID=DBA;PWD=sql" 
   -x https(
     identity=c:\%SQLANYSAMP16%\Certificates\rsaserver.id;
     identity_password=test)

On a SQL Anywhere client, the implementation is:

dbmlsync 
   -c "DSN=mydb;UID=DBA;PWD=sql" 
   -e "ctp=https;
       adr='trusted_certificates=c:\%SQLANYSAMP16%\Certificates\rsaroot.crt;
          certificate_name=RSA Server"
          certificate_company=test;
          certificate_unit=test'"

On an UltraLite client, the implementation is:

info.stream = "https";
    info.stream_parms = 
       "trusted_certificates=\%SQLANYSAMP16%\Certificates\rsaroot.crt;"
       "certificate_name=RSA Server;"
       "certificate_company=test;"
       "certificate_unit=test";