Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 11.0.1 (Français) » SQL Anywhere Server - Database Administration » Starting and Connecting to Your Database » Connection parameters and network protocol options » Network protocol options

 

certificate_name protocol option

Forces the client to accept server certificates only when the Common Name field on the certificate matches this value.

Composants nécessaires sous licence distincte

Les cryptages ECC et certifié FIPS exigent une licence distincte. Toutes les technologies de cryptage fort sont soumises à la réglementation en matière d'exportation.

Pour plus d'informations, reportez-vous à la section Separately licensed components.

Syntax
certificate_name=common-name
Usage

TLS, HTTPS

Default

None

Remarks

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).

See also
Example

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')"