trusted_certificates protocol option

trusted_certificates=public-certificate

TLS, HTTPS

None

Clients use the trusted_certificates encryption protocol option to specify trusted database server certificates. The trusted certificate can be a server's self-signed certificate, a public enterprise root certificate, or a certificate belonging to a commercial Certificate Authority. If you are using FIPS-certified RSA encryption, you must generate your certificates using RSA. If TLS is specified in the Encryption connection parameter, this protocol option is required.

Note

trusted_certificate is also accepted.

HTTPS is only supported for web services client procedures. See CREATE PROCEDURE statement [Web service].

Note

Separately licensed component required.

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

See Separately licensed components.

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(
FIPS=n;trusted_certificates=c:\temp\myident;
certificate_unit='SA';certificate_company='Sybase iAnywhere';
certificate_name='Sybase')"