OBKV-Table currently supports identity authentication and transparent data encryption.
Identity authentication
OBKV-Table uses APIs for access, which differs from SQL-based authentication. OBKV-Table performs identity authentication over TCP connections. The principle is similar in both direct connection mode and ODP mode:
- After a TCP connection is established, the first message sent is always a Login message. This message contains the cluster name, tenant name, username, password, salt, and other information.
- After authentication by using the username and password, the database generates a credential for the client. Each subsequent message includes this credential. Before processing a message, the database verifies the validity of the credential. Only valid credentials allow data access.
- The credential also includes an expiration time. After the credential expires, the database server refuses to provide services.
Transparent data encryption
Data storage encryption, also known as transparent data encryption (TDE), encrypts data and metadata stored on disk in a transparent manner. Data is automatically encrypted before being written to storage devices and automatically decrypted when read. This process is transparent to users and prevents malicious actors from reading sensitive data from files, database backups, or disks.
To protect data stored in memory and on hard drives, OceanBase AI Database currently supports the internationally prevalent AES encryption algorithm, as well as the domestically developed SM4 algorithm.
For more information about transparent data encryption, see the following topics:
- For an overview of transparent data encryption, see Transparent data encryption overview.
- For detailed operations on transparent data encryption, see: