Currently, OBKV-HBase supports identity authentication and transparent data encryption.
Identity authentication
Access to OBKV-HBase is performed through APIs, so identity authentication in OBKV-HBase differs from that in an OceanBase AI Database SQL cluster. OBKV-HBase implements identity authentication based on TCP connections. The working mechanism is the same whether you connect to OBKV-HBase directly or by using ODP:
- After a TCP connection is established, the first message is a login message. This message carries login information such as the cluster name, tenant name, username, password, and salt value.
- After the database authenticates the identity based on the username and password, it generates a credential for the client, which is carried and verified in each subsequent message. The client can access data only if the carried credential is verified to be valid.
- Each credential has a validity period. After a credential expires, the database server refuses to provide services.
Transparent data encryption
Data storage encryption refers to transparent data encryption of data and CLOGs stored on disks, also known as transparent data encryption (TDE). Data is automatically encrypted before it is written to a storage device and automatically decrypted when it is read. This process is transparent to users. Hackers and malicious users cannot read sensitive data from files, database backups, or disks.
To protect the security of data stored in memory and on disks, OceanBase AI Database supports the internationally standard AES encryption algorithm and the Chinese national cryptographic algorithm SM4.
The references for transparent data encryption are as follows:
- For an overview of transparent data encryption, see Overview of transparent data encryption.
- For detailed operations, see: