Provide hashed clientID to amo for abuse report verification.
Categories
(Toolkit :: Add-ons Manager, defect, P2)
Tracking
()
People
(Reporter: scolville, Unassigned)
References
Details
This is currently sent to the disco pane in a header to facilitate recommendations.
This is to support updates to the abuse report flow on AMO which will be changed to match the one being built for Firefox in bug 1540175. We want to be able to verify the abuse reports filed from the site as well as from Firefox.
The verification will happen via a telemetry lookup (This will be a server to server call, the endpoint is covered in https://github.com/mozilla/taar/issues/151) to be able to make that call we need the hashed clientID.
The exact mechanism for how to do this should be discussed. For this specific need it doesn't need to be sent in the request, but, if we do want the clientID for additional recommendations changes on AMO in the future that would need the clientID to be sent in a request.
As before the clientID should not be sent/available if telemetry is disabled.
|
||
Updated•5 years ago
|
|
||
Comment 1•5 years ago
|
||
Hi Stuart,
I'm closing this as wontfix because we have opted for the alternative strategy implemented in Bug 1580561.
Description
•