LG-7347 Limit use of ThreatMetrix to certain service providers#6914
Merged
LG-7347 Limit use of ThreatMetrix to certain service providers#6914
Conversation
stevegsa
commented
Sep 2, 2022
…to certain service providers
zachmargolis
reviewed
Sep 2, 2022
db/primary_migrate/20220902162411_add_allow_threatmetrix_to_service_providers.rb
Outdated
Show resolved
Hide resolved
db/primary_migrate/20220902162411_add_allow_threatmetrix_to_service_providers.rb
Outdated
Show resolved
Hide resolved
stevegsa
commented
Sep 2, 2022
aduth
reviewed
Sep 6, 2022
zachmargolis
reviewed
Sep 6, 2022
NatashaJIbrahim
approved these changes
Sep 6, 2022
Merged
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
5 participants
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.
Why: To limit threatmetrix service
How: Add
device_profiling_enabledto service_provider table. Use a two prong approach. 1) Disable any generation of a threatmetrix_session_id which will also disable the javascript for device profiling and 2) make sure that a threatmetrix call is never made by checking the backend. Add issuer to the resolution_proofing_job proofing call so that the backend job can ascertain the setting for the sp. Addno_sp_device_profiling_enabledfor the case where the user goes in directly