sp_remoteoption

Displays or changes remote login options.

Syntax

sp_remoteoption [remoteserver[, loginame 
	[, remotename[, optname[, optvalue]]]]]

remoteserver – is the name of the server that executes RPCs on this server.
Note: This manual page uses the term “local server” to refer to the server that is executing the remote procedures that are run from a “remote server.”
loginame – is the login name that identifies the local login for the remoteserver, loginame, remotename combination.
remotename – is the remote user name that identifies the remote login for the remoteserver, loginame, remotename combination.
optname – is the name of the option to change. Currently, there is only one option, trusted, which means that the local server accepts remote logins from other servers without user-access verification for the particular remote login. The default is to use password verification. The SAP ASE server understands any unique string that is part of the option name. Use quotes around the option name if it includes embedded blanks.
optvalue – is either true or false. true turns the option on, false turns it off.

Example 1 – Displays a list of the remote login options:

sp_remoteoption

Settable remote login options.
remotelogin_option 
------------------------ 
trusted

Example 2 – Defines the remote login from the remote server GATEWAY to be trusted; that is, the password is not checked:
```
sp_remoteoption GATEWAY, churchy, pogo, trusted, true
```
Example 3 – Defines the remote login “pogo” from the remote server GATEWAY as a login that is not trusted; that is, the password is checked:
```
sp_remoteoption GATEWAY, churchy, pogo, trusted, false
```
Example 4 – Defines all logins from GATEWAY that map to login “albert” on the local server to be trusted:
```
sp_remoteoption GATEWAY, albert, NULL, trusted, true
```

There are additional considerations when using sp_remoteoption:

To display a list of the remote login options, execute sp_remoteoption with no parameters.
If you have used sp_addremotelogin to map all users from a remote server to the same local name, specify trusted for those users. For example, if all users from server GOODSRV that are mapped to “albert” are trusted, specify:
```
sp_remoteoption GOODSRV, albert, NULL, trusted, true
```
If the logins are not specified as trusted, they cannot execute RPCs on the local server unless they specify local server passwords when they log into the remote server. When they use Open Client Client-Library, users can specify a password for server-to-server connections with the routine ct_remote_pwd. isql and bcp do not permit users to specify a password for RPC connections.

If users are logged into the remote server using “unified login”, the logins must also be trusted on the local server, or they must specify passwords for the server when they log into the remote server.

See the System Administration Guide for more information about setting up servers for remote procedure calls and for using “unified login.”

The permission checks for sp_remoteoption differ based on your granular permissions settings.

Setting	Description
Enabled	With granular permissions enabled, you must be a user with `manage any remote login` privilege.
Disabled	With granular permissions disabled, you must be a user with sso_role.

Values in event and extrainfo columns from the sysaudits table are:

Information	Values
Event	38
Audit option	exec_procedure
Command or access audited	Execution of a procedure
Information in `extrainfo`	Roles – Current active roles Keywords or options – NULL Previous value – NULL Current value – NULL Other information – All input parameters Proxy information – Original login name, if set proxy in effect