decrypt payload for authenticated data#18
Open
caseThree wants to merge 1 commit intotruecaller:masterfrom
Open
decrypt payload for authenticated data#18caseThree wants to merge 1 commit intotruecaller:masterfrom
caseThree wants to merge 1 commit intotruecaller:masterfrom
Conversation
This file contains hidden or 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.
The truecaller profile received at the backend is of this format:
{
"avatarUrl":null,
"city":null,
"companyName":null,
"countryCode":"IN",
"email":null,
"facebookId":null,
"firstName":"Shobhit",
"gender":"M",
"isAmbassador":false,
"isBusiness":false,
"isVerified":false,
"jobTitle":null,
"lastName":"Tewari",
"payload":null,
"phoneNumber": null,
"requestNonce": null,
"signature": null,
"street":null,
"successful":true,
"twitterId":null,
"url":null,
"zipcode":null
}
Here null is the placeholdere for specific fields.
In this format of data, we verify the signature but there is a possibility that the developer may take data from the raw object mentioned above. After validation, the data must be taken from the payload and not the raw object received at the backend as shown above. This is also mentioned in the docs.
I created a function that will return the details in the payload which is the verified data in the format:
{
requestNonce: null,
requestTime: null,
phoneNumber: null,
firstName: 'Shobhit',
lastName: 'Tewari',
gender: 'M',
countryCode: 'IN',
trueName: true,
ambassador: false,
isBusiness: false,
verifier: null
}
This is the data which is received after decoding the payload which is verified after verifying the signature.