Mask fields when request is string #102
Merged
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.
Description
Mask sensitive fields when request is a string. The only times I have managed to see request come in as a string is when Adyen web service user has a missing permission.
Due to the fact that we parse request string into a hash inside of the
mask_fields
method, the current code doesn't modify the original request and it preserves the original request data without masking any of the fields.Additionally, while parsing it wasn't symbolising the name which meant, further down we were comparing string with symbols here
Tested scenarios
Fixed issue: