Quick Audience:Organization System Configuration

AES encryption function

AES is a symmetric encryption algorithm that uses the same key for encryption and decryption.

If the ID field is stored in MaxCompute, ADB3.0, or MySQL, you can use the following functions to encrypt and decrypt the ID.

MaxCompute

Before you begin, download the AES Encryption and Decryption Function Code Package. Then, run the following commands on the MaxCompute CLI to register the custom functions:

add jar crypt-1.0-SNAPSHOT.jar as crypt.jar;
create function qa_aes_encrypt as 'com.aliyun.quicka.crypt.AESEncrypt' using 'crypt.jar';
create function qa_aes_decrypt as 'com.aliyun.quicka.crypt.AESDecrypt' using 'crypt.jar';

Example of AES encryption and decryption:

-- Encrypt "China" and convert it to Base64. The key is "xxxxxxxxxxxxxxxx". 
select qa_aes_encrypt ('China', xxxxxxxxxxxxxxxx);
-- The result is CjUlHjFp8lEUOfQ4k5eCpA==. 

-- Decrypt "CjUlHjFp8lEUOfQ4k5eCpA==", "xxxxxxxxxxxxxxxx" is the same key. 
select qa_aes_decrypt('CjUlHjFp8lEUOfQ4k5eCpA==', 'xxxxxxxxxxxxxxxx');
-- The result is "China". 

ADB3.0

ADB3.0 provides built-in AES encryption and decryption functions.

Example of AES encryption and decryption:

-- Encrypt "China" and convert it to Base64. The key is "xxxxxxxxxxxxxxxx". 
select TO_BASE64(aes_encrypt(CAST ('China' AS VARBINARY), xxxxxxxxxxxxxxxx))
-- The result is CjUlHjFp8lEUOfQ4k5eCpA==. 

-- Decrypt "CjUlHjFp8lEUOfQ4k5eCpA==", "xxxxxxxxxxxxxxxx" is the same key. 
select aes_decrypt(FROM_BASE64('CjUlHjFp8lEUOfQ4k5eCpA=='), 'xxxxxxxxxxxxxxxx') 
-- The result is "China". 

MySQL

MySQL provides built-in AES encryption and decryption functions.

Example of AES encryption and decryption:

-- Encrypt "China" and convert it to Base64. The key is "xxxxxxxxxxxxxxxx". 
select TO_BASE64(AES_ENCRYPT ('China', 'China')); xxxxxxxxxxxxxxxx
-- The result is CjUlHjFp8lEUOfQ4k5eCpA==. 

-- Decrypt "CjUlHjFp8lEUOfQ4k5eCpA==", "xxxxxxxxxxxxxxxx" is the same key. 
select AES_DECRYPT(FROM_BASE64('CjUlHjFp8lEUOfQ4k5eCpA=='), 'xxxxxxxxxxxxxxxx')
-- The result is "China". 

Short chain domain switching

To switch from an old domain to a new domain while preserving the validity of existing short chains, follow these steps:

1. Pre-switchover operations:

   • Check the new short chain domain information:

     • Check whether the HTTPS certificate of the new domain is ready.

     • Check whether the DNS of the new domain points to the IP address resolved from the original domain.

     • Check whether Nginx forwarding is configured for the new domain. Use the original domain configuration as a reference. Otherwise, the new domain may be inaccessible.

   • Check existing short-chain marketing activities: Verify whether any active marketing campaigns are sending messages, including text messages in SMS Marketing and Automatic Marketing. If yes, ensure the corresponding short-chain domain remains accessible within the short chain's validity period.

     (Optional) If you have an active campaign sending regular short chains, create a test campaign that only sends regular short chains to verify they can be sent and accessed after the domain switch.

2. On the Organization System Configuration page, save the new domain.

   Note

   • The new domain takes effect immediately after it is saved. New short chains created later will use the new domain.

   • The original short chain is not affected. If the original domain is accessible, the original short chain can continue to be used.

3. Check after switching:

   • Test the new short chain: Copy a new short chain to your browser's address bar and verify that it resolves to the correct long URL.

   • (Optional) Test the original short chain: Run the test campaign created in Step 1 to send only the original short chain. Verify that the original short chain can still be sent and accessed. After the test, delete the test campaign.