certificate_company protocol option

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

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

certificate_company=organization

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