For RPC security model B, you can set options with the sp_serveroption system procedure. The syntax is:
sp_serveroption server, optname, optvalue
where:
server – is the name of the remote server.
optname – is the name of the option. Values can be:
security mechanism – the name of the security mechanism to use when running an RPC on a remote server.
mutual authentication – set this option to 1 to cause the local Adaptive Server to authenticate and verify the remote server. If this parameter is 0 (the default), the remote server still verifies the local server when it sends an RPC, but the local server does not check the validity of the remote server.
use message confidentiality – set this option to 1 to cause all messages for the RPCs to be encrypted when they are sent to the remote server and received from the remote server. If this parameter is 0 (the default), data for the RPCs will not be encrypted.
use message integrity – set this option to 1 to require that all RPC messages be checked for tampering. If this parameter is 0 (the default), RPC data will not be checked for tampering.
optvalue – must be equal to “true” or “false” for all values of optname, except security mechanism. If the option you are setting is security mechanism, specify the name of the security mechanism. To find the list of security mechanisms, execute:
select * from syssecmechs
For information about the syssecmechs system table, see “Determining enabled security services”.
For example, to set up the local server to execute RPCs on a remote server, TEST3, which will use the “dce” security mechanism, and to use mutual authentication for all RPCs between the two servers, execute:
sp_serveroption TEST3, "security mechanism", dce sp_serveroption TEST3, "mutual authentication", true
