Adaptive Server accepts client logins and server-to-server RPCs. The address and port numbers where Adaptive Server accepts connections are configurable so you can specify multiple networks, different protocols, and alternate ports.
In the interfaces file, SSL is specified as a filter on the master and query lines, whereas security mechanisms such as DCE or Kerberos are identified with a SECMECH line. The following example shows a TLI-based entry for an Adaptive Server using SSL in a UNIX environment:
An entry for an Adaptive Server with SSL and DCE security mechanisms on UNIX might look like:
SYBSRV1 master tcp ether myhostname myport1 ssl query tcp ether myhostname myport1 ssl master tcp ether myhostname myport2 SECMECH 1.3.6.1.4.897.4.6.1
An entry for the server with SSL and Kerberos security mechanisms on Windows might look like:
[SYBSRV2] query=nlwnsck, 18.52.86.120,2748,ssl master=nlwnsck 18.52.86.120,2748,ssl master=nlwnsck 18.52.86.120,2749 secmech=1.3.6.1.4.897.4.6.6
The SECMECH lines for SYBSRV1 and SYBSRV2 in the examples contain an object identifier (OID) that refers to security mechanisms DCE and Kerberos, respectively. The OID values are defined in:
UNIX – $SYBASE/$SYBASE_OCS/config/objectid.dat
Windows – %SYBASE%\%SYBASE_OCS\ini\objectid.dat
In these examples, the SSL security service is specified on port number 2748(0x0abc).
The use of SSL concurrently with a SECMECH security
mechanism is intended to facilitate migration from SECMECHs to SSL
security.
