certificate_name=common-name

TLS, HTTPS

None

SQL Anywhere 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 database 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.

HTTPS is only supported for web services client procedures. See CREATE PROCEDURE statement (web clients).

• certificate_company protocol option
• certificate_unit protocol option
• trusted_certificates protocol option
• Encryption (ENC) connection parameter
• Encrypting SQL Anywhere client/server communications
• Certificate Creation utility (createcert)
• -xs dbeng12/dbsrv12 server option

The following command connects the SQL Anywhere sample database to Interactive SQL using transport-layer security.

dbisql -c 
"UID=DBA;PWD=sql;HOST=myhost;Server=demo;ENC=TLS(
tls_type=RSA;FIPS=n;trusted_certificates=c:\temp\myident;
certificate_unit='SA';certificate_company='Sybase iAnywhere';
certificate_name='Sybase')"