Specifying an RPC security model

The security model controls the level of security applied to the connections made between local and remote servers when a remote server executes an RPC. Depending on the security mechanism you use, RPC security provides mutual authentication, message confidentiality, and message integrity for remote procedure communications.

You can specify one of two RPC security models, A or B. Model A is equivalent to the level of security in Sybase SQL Server version 11.0.x and prior versions.

In security model B the local Adaptive Server gets a credential from the security mechanism and uses the credential to establish a secure physical connection with the remote Adaptive Server. You can use one or more of the following security services:

Mutual authentication – the local server authenticates the remote server by retrieving the credential of the remote server and verifying it with the security mechanism. With this service, the credentials of both servers are authenticated and verified.
Message confidentiality via encryption – messages are encrypted when sent to the remote server, and results from the remote server are encrypted.
Message integrity – messages between the servers are checked for tampering.

Security model B implements security using on of the following security mechanisms:

Distributed Computing Environment (DCE) (UNIX)
CyberSAFE Kerberos (UNIX)
NT LAN Manager (Windows NT)

You can configure RPC security in the Remote Server property sheet.