certificate_name

If specified, the application only accepts server certificates when the Common Name field on the certificate matches this value.

Separately licensed component required

ECC encryption and FIPS-certified encryption require a separate license. All strong encryption technologies are subject to export regulations.

See Separately licensed components.

Syntax
certificate_name=common-name
Protocols
Default

None

Remarks

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 Network protocol options for UltraLite synchronization streams.

See also
Example

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.

On the server, the implementation is:

mlsrv11 
   -c "dsn=SQL Anywhere 11 Demo;uid=DBA;pwd=sql" 
   -x https(
     port=9999;
     identity=c:\sa10\bin32\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='port=9999;
         trusted_certificates=c:\sa10\bin32\rsaroot.crt;
         certificate_name=RSA Server'"

On an UltraLite client, the implementation is:

    info.stream = "https";
    info.stream_parms = TEXT(
      "port=9999;
       trusted_certificates=\sa10\bin32\rsaroot.crt;
       certificate_name=RSA Server");