[feature] Desensitize sensitive information(new) #2859
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's changed?
#2792
Yes, this PR is a brand new version, I used Caffeine to cache the key as id+ desensitized data, the value as undesensitized data, and when the desensitized data is passed in by the front end, it is converted to undesensitized data, which has been verified.
Using id + desensitized data as key can avoid confusion of value when other desensitized data is the same
Here is a picture of the modification operation:
Here are the tests sent:
Here is a picture of the database:
Checklist
Add or update API