certificate_name=common-name

• TLS, HTTPS

None

MobiLink clients trust all certificates signed by the certificate authority, so they may also trust certificates that the same certificate authority has issued to other companies. Without a means to discriminate, your clients might mistake a competitor's MobiLink server for your own and accidentally send it sensitive information. This option specifies a further level of verification, that the Common Name field in the identity portion of the certificate also matches a value you specify.

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.

• MobiLink client/server communications encryption
• Verifying certificate fields
• -x mlsrv16 option
• trusted_certificates
• certificate_company
• 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";