Automatically encrypt data with the latest version of the key

Data can be transferred in batches and returned in batches

Automatically encrypt data with the previous version key (may be used during key change migration)

Can be transferred in batches Enter data and return in batches

Automatically determine the ciphertext version and decrypt it with the corresponding version key Data

can be imported in batches and returned in batches

Generate Fuzzy query for a given string

Initialization:

## SecurityClient SecurityClient = new SecurityClient(new DefaultTaobaoClient(serverUrl, appkey, appSecret), randomNumber)

Note 1: The serverUrl used by defaultTaobaoClient must be https protocol

Encryption:

securityClient.encrypt(“13888883333”, type, sessionKey)

Ciphertext judgment:

SecurityClient.isEncrypt(“13888883333”, type)

Previous version key encryption:

Decryption: ##securityClient.decrypt(“~CKoqAl2hWzh54uBFv9Suug==~1~”, type, sessionKey)

String searchIndex = securityClient. search(“3333”, type, sessionKey)

SELECT * FROM table_orders WHERE phone LIKE #searchIndex#%

##( This example is a mobile phone number. For other examples, please refer to the scene details below)

Encryption calling specification:

1) All use the session key of the main account. The sub-account may not have permissions

2) Pre-judge the session key before calling

3) Authorization returns sessionkey with expiration time

4) Determine whether the expiration time of the session key has exceeded 90 days. If the expiration date exceeds 90 days, there is no need to call encryption or decryption (it will never succeed before re-authorization, which is a waste of resources). Assume that there is an error on the client side. Judgment, the actual call to encryption and decryption may throw an exception. The following solution can be used:

try {

// Encryption and decryption operations

##} catch (SecretException e) {

if(ErrorUtil.isInvalidSession(e)) {

// Mark the sessionkey as invalid before re-authorization Do not call

}

}

2.3Code scenario example:

1) Initialization:

SecurityClient securityClient

= new SecurityClient (new DefaultTaobaoClient(serverUrl, appkey, appSecret), Random Number);

defaultTaobaoClient serverUrl must be https protocol, currently it is https: //eco.taobao.com/router/rest (Sandbox environment: https://gw.api.tbsandbox.com/router/rest)

2) Encryption and decryption:

receiver_mobile The encryption field type (type) is phone. Other encrypted field types (type) are based on the field query method: the field type (type) of the ordinary encryption method is simple, the field type (type) of the fuzzy query is search.

Encryption and decryption Input parameters must bring sessionkey

Output result:

Plain text of mobile phone number: 13834566786 -> Encrypted text: $138$SuR h6AtlSj8Z59W2W9EQ==$103$

## Encrypted text of mobile phone number: $138$SuR h6AtlSj8Z59W2W9EQ==$103$ ->Clear text: 13834566786

============================TOP====== =================

Batch encryption and decryption

##Output result

：##Mobile phone number Plain text: 15923847823 -> Encrypted text: $159$AtyBFui4xvl92WV7GKwfBw ==$103$

Mobile phone number plain text: 13834566786 ->Private text: $138$SuR h6AtlSj8Z59W2W9EQ==$103$

Mobile phone number secret text Text: $138$SuR h6AtlSj8Z59W2W9EQ==$103$ -> Plain text: 13834566786

4) Normal encryption scenario:

Scenario 1: does not appear in the where clause in the SQL statement. Directly get the data to decrypt and display or print:

String cipher = ReadFromDataBase(); // SELECT cipher FROM table...

##String phone = securityClient.decrypt(cipher, “phone”, sessionKey);

Scenario 2: Need to encrypt The fields are put into the where clause (key = “value”) as SQL search conditions:

                    String cipher = securityClient.encrypt(p, “phone”, sessionKey);

# SELECT * From Table where Phone = #cipher

In the process of switching to the cipher text, there may be a mixed existence of confistent texts and ciphertexts. temporary state. This requires preparation for compatibility:

SELECT * FROM table WHERE phone in (#cipher#, #p#)

##5) Support fuzzy query encryption scenarios (non-mobile phone number fields)：

Scenario 1: Non-mobile phone number field fuzzy query sample code:

//Get the fuzzy query ciphertext
String search = securityClient.search(partial);

//Go Database fuzzy query
List<DO> objects = SELECT * FROM table WHERE nick LIKE “%” #search# “%”

// Filter
List<DO> result = new List<DO>();

for(DO object : objects) {
if (SecurityClient.decrypt(object.nick).contains(partial)){
result.add(object);
}
}

Scenario 2:phone fuzzy query top 3 Sample code:

(prefix index will be used)

//Fragments that require fuzzy query

String partial = "138";

## // Go to the database to do fuzzy query
List<DO> objects = SELECT * FROM table WHERE nick LIKE “$” partial “%”

## Scenario 3: phone fuzzy query The last 4 digits of sample code:

//Get the fuzzy query ciphertext
String search = securityClient.search(partial);
// Go to the database to do fuzzy query
List<DO> objects = SELECT * FROM table WHERE nick LIKE partial “%”

FAQ

• There is no FAQ about this document

php.cn

HomeCourseArticleQ&ADictionaryManualDownloadsearch APPDownload