Fix: Obfuscate email and phone in profileDiff response #2205
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Date: 08 Oct 2024
Developer Name: @lakshayman
Issue Ticket Number
#2204
Description
This PR addresses an issue where the email and phone fields were not being obfuscated in the
profileDiffresponse. It adds checks to obfuscate the email and phone fields before sending the response back to the client. This ensures that sensitive user data is protected.Documentation Updated?
No documentation updates were needed as this was an internal bug fix related to obfuscation.
Under Feature Flag
This fix is applied globally and is not gated by a feature flag.
Database Changes
No database changes were required for this fix.
Breaking Changes
There are no breaking changes associated with this update.
Development Tested?
This fix has been tested locally.