Help Center/ Database Security Service/ User Guide/ Database Encryption/ Series 2/ Quick Start/ Scenario 2: Proxy Pattern - Pre-release Phase/ Proxy Pattern - Pre-release Phase Process
Updated on 2026-09-24 GMT+08:00
View PDF
Share

Proxy Pattern - Pre-release Phase Process

This scenario uses the MySQL database as an example to illustrate the integration of the Proxy. This scenario covers only MySQL; for other databases, please refer to the System Administrator Operation Guide. To use the Proxy pattern, follow these steps:

  1. Logging In to the Database Encryption System using the system administrator (sysadmin) account.
  2. Creating an Asset Database: Bind the business database to integrate system data sources.
  3. Creating a Project: provides a multi-project encryption management environment that enables clear management of encryption operations across various real-world projects and facilitates isolated management across different projects.
  4. Configuring the Main Server: the main server is the host machine on which the encrypted proxy service runs. Depending on the operating environment, the main server can be either a cloud-based host or a physical host; technically, a single main server can host multiple encrypted proxy services.
  5. Configuring the Proxy Service: set up the database proxy service; this service serves as the primary execution unit responsible for data encryption and decryption.
  6. Third-party Software Proxy Connectivity Test: Verify that network links are functioning properly and proactively troubleshoot any network or service anomalies.
  7. Modifying the Integrated System's Database Connection: switch the database access pathway to an encrypted proxy to handle all data read/write requests.
  8. Testing the Application: Restart the business application and launch the encrypted proxy service to verify that data encryption/decryption and the business processes are functioning normally.

Constraint Application

  • Special note regarding whether to enable SSL: To encrypt non-intrusive bypass traffic, the TLS encrypted channel cannot be used, which may pose security risks.
  • Encrypted proxy functionality; currently unsupported data operation methods:
    • The `SELECT` data type clause that includes the `temp` keyword is not currently supported.
    • `INSERT` is used for batch insertion of data with a self-referential structure; `INSERT` supports nested formatting.
    • Update: The data type supports nested formatting.
    • encrypted fields do not support size comparison operators (e.g.,>, <, ORDER BY, BETWEEN, etc.).
    • Function computations (e.g., AVG, MAX, MIN, SUM, and arithmetic expressions) are not supported.
    • View, trigger, and stored procedure operations are not supported; for equality comparisons ('=') following conditions such as 'WHERE', both fields on either side of the '=' operator must be encrypted, or neither field should be encrypted.
    • Encryption for table or field names containing wildcards is not supported for configuration.
Parent Topic: Scenario 2: Proxy Pattern - Pre-release Phase