Updated on 2026-07-07 GMT+08:00

Database

Through the Data Source Asset Library module, users can efficiently manage various data source assets, ensuring data availability and security while providing a foundation for subsequent data encryption and anonymization operations.

Apply Constraint

Special clarification on whether to enable SSL:

Currently, due to business restrictions, enabling SSL will only support MySQL 8.4 version, and certificate authentication exemption needs to be enabled.

Table 1 Table1 Data sources and versions supported by database encryption

Database

Version

MySQL

  • 5.7
  • 8.4

Mariadb

11

Oracle

12c

SQLServer

2022

Postgres

13.2

Greenplum

12

Dreamland

8.1

DB2

11.5

Renmin University of China Jinkang Kingbase

V008R006C009B0014

DWS

9.2

Gaussdb

9.2

OpenGauss

3.0.0

RDS for MYSQL

8

RDS for PostgreSQL

13.23

RDS for MariaDB

10.11

RDS for SQL Server

15.00.4375

RDS for TaurusDB

8.0.22-30

Add data source

  1. Logging In to the Database Encryption System using the system administrator sysadmin account.
  2. In the left navigation bar, select Database.
  3. In the right pane, click Add Data Source.

    Figure 1 Create a new data source

  4. In the new page, select the database type.

    Figure 2 Select a database type

  5. After selecting the required database type, proceed to the configuration page (using MySQL database as an example).

    Figure 3 Configurating information
    Table 2 Table2 Data source configuration form parameter description

    Parameter

    Description

    Data source name

    Customizable name (no special characters). Length ≤ 25 characters.

    Connection Type

    Displayed only when Data Source Type is ORACLE.

    Options:

    • Service Name.
    • SID.

    Service Name

    Displayed only when Data Source Type is ORACLE.

    Custom service name.

    Address

    IP address or domain name for database connection (supports IPv4/IPv6).

    Port

    The port for accessing the database, such as MySQL's 3306.

    Database Name

    Name of the target database for encryption/masking. Not displayed for ORACLE.

    Username

    Authentication credential for database access.

    Password

    Authentication credential for database access.

    Database version

    Auto-generated by clicking Detect Version.

    Character encoding

    Supported encodings:

    • When the data source type is MYSQL, POSTGRESQL, or MSSQLSERVER, the following character encodings are available:
      • UTF8
      • GBK
    • When the data source type is ORACLE, the following character encodings are available:
      • AL32UTF8
      • ZHS16GBK
    • When the data source type is DB2, the following character encodings are available:
      • Unicode
      • UCS-2
      • UTF16
      • UTF8

  6. Fill in the required configuration information and click Confirm to save. (It is recommended to click the Test button for verification before saving).

View data source

View the configuration information of all data sources. The page supports fuzzy matching queries based on conditions.

Figure 4 Browse the data source

Edit or delete

Adjust the configuration of existing data sources to accommodate changing business requirements.

  1. Logging In to the Database Encryption System using the system administrator sysadmin account.
  2. In the left navigation bar, select Database.
  3. Click the data source you want to modify, and the corresponding configuration information will appear on the page.

    Figure 5 Modifying data source information
    1. Click Edit to modify the information and select the Test button. Click Confirm to save.
    2. You can delete the data source as needed.
      Figure 6 Deleting data source information

  • Data loss: Encryption, decryption, or desensitization operations depend on specific data source configurations. If the data source is edited or deleted while these operations are in progress, the relevant data may not be decrypted or recovered correctly, resulting in data loss.
  • System failure: Rule configuration, encryption/decryption, and data masking operations are typically tightly integrated with other system components. Editing or deleting data sources while these operations are in progress may cause system failures and disrupt normal system operation.
  • Security Risk: Encryption, decryption, and data masking operations involve handling sensitive data. Editing or deleting the data source while these operations are in progress may create security vulnerabilities, exposing sensitive data to risk.