Forces the client to accept server certificates only when the Common Name field on the certificate matches this value.
ECC encryption and FIPS-certified encryption require a separate license. All strong encryption technologies are subject to export regulations.
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 services).
The following command connects the SQL Anywhere sample database to Interactive SQL using transport-layer security.
dbisql -c "UID=DBA;PWD=sql;ENG=demo;LINKS=tcpip;ENC=TLS( tls_type=RSA;FIPS=n;trusted_certificates=c:\temp\myident; certificate_unit='SA';certificate_company='Sybase iAnywhere'; certificate_name='Sybase')"
|Discuss this page in DocCommentXchange.
Send feedback about this page using email.
|Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1|