trusted_certificates protocol option

Specifies the path and file name of a file that contains one or more trusted certificates.

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
trusted_certificates=public-certificate
Usage

TLS, HTTPS

Default

None

Remarks

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-approved RSA encryption, you must generate your certificates using RSA. If TLS is specified in the Encryption connection parameter, this protocol option is required.

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