rpc_server_authentication_method specifies the security authentication method of the RPC server. You only need to log on to the sys tenant and set the authentication method for the client and server by running corresponding commands.
Note
This parameter was introduced in OceanBase Database V3.2.4.
| Attribute | Description |
|---|---|
| Type | String |
| Default value | ALL |
| Value range |
|
| Effective upon OBServer node restart | No |
Example
ALTER SYSTEM SET rpc_server_authentication_method = 'ALL';
ALTER SYSTEM SET rpc_server_authentication_method = 'NONE';
Considerations
You need to specify the
rpc_client_authentication_methodparameter for the client. For more information, see rpc_client_authentication_method.The server supports multiple authentication methods. If you set multiple authentication methods at a time, separate the authentication methods with commas (,). The parameter value is case-insensitive.
ALTER SYSTEM SET rpc_server_authentication_method = 'NONE, SSL_NO_ENCRYPT';If the parameter is set to a correct value, the latest specified value is used. Otherwise, the original authentication method is used. For example, if you change the value from
NONEtoSSL_NO_ENCRYPT, ANYby running thealter system set rpc_server_authentication_methodcommand, the original valueNONEis still used. This is becauseANYis not a valid value.The following table describes the types of clients that are allowed based on the value of the rpc_server_authentication_method parameter:
Value of rpc_server_authentication_method Types of clients allowed NONE - Old clients that have not been upgraded or authenticated
- New clients whose authentication method is
NONE
SSL_NO_ENCRYPT New clients whose authentication method is SSL_NO_ENCRYPTALL The union of the preceding types