rpc_server_authentication_method

Last Updated:2026-09-03 07:27:35

This parameter is available starting with V3.2.4.

Description

rpc_server_authentication_method specifies the authentication method for the RPC server.

For the sys tenant, you only need to set the authentication method on the client and server.

Query the parameter

The sys tenant and all user tenants can use the SHOW PARAMETERS statement or the GV$OB_PARAMETERS view to query this parameter.
Modify the parameter

Only the sys tenant can modify this parameter. User tenants cannot modify this parameter.

Attribute	Description
Type	String
Default value	ALL
Value range	NONE: no authentication is performed. For high-security scenarios, we recommend that you disable `NONE` on the server. ALL: the default authentication method for the server, which supports any authentication method (NONE, SSL_NO_ENCRYPT). SSL_NO_ENCRYPT: authentication is performed by using the local SSL certificate and private key through the SSL handshake, but subsequent communication is not encrypted.
Modifiable	Yes. You can use the `ALTER SYSTEM SET` statement to modify the parameter.
Effective upon OBServer node restart	No. The setting takes effect immediately.

On the client, set the rpc_client_authentication_method parameter. For more information, see rpc_client_authentication_method.
The server supports multiple authentication methods. When you set multiple authentication methods, separate them with commas. This parameter is case-insensitive.
```
ALTER SYSTEM SET rpc_server_authentication_method = 'NONE, SSL_NO_ENCRYPT';
```
If all the values of the parameter are correctly set, the latest setting takes effect. Otherwise, the original authentication method remains in effect, and the current setting does not take effect. For example, the original authentication method is NONE. You set alter system set rpc_server_authentication_method = 'SSL_NO_ENCRYPT, ANY'; (but ANY is not a valid value). In this case, the current setting does not take effect, and the server authentication method remains NONE.

The following table describes the client types that are allowed to connect to the server based on the server parameter value.

Server parameter value	Allowed client types
NONE	Old clients that are not upgraded (including unauthenticated clients) New clients with the `NONE` authentication method
SSL_NO_ENCRYPT	New clients with the `SSL_NO_ENCRYPT` authentication method
ALL	The sum of the two cases above

Set the authentication method for the RPC server to ALL.

obclient> ALTER SYSTEM SET rpc_server_authentication_method = 'ALL';

Previous topic

Next topic