814244 - ToS acceptance check for sync2.0?

Status: VERIFIED FIXED

(Cloud Services Graveyard :: Server: Sync, defect)

Description

[Ryan Kelly [:rfkelly]]

Should we implement an explicit Terms-of-Service acceptance check for Sync2.0, along the same lines as the one we added in AitC?

(IIUC this just means flipping some switches in the product database inside tokenserver, but we should at least call this out in the sync2.0 docs)

Comment 1

[Richard Newman [:rnewman]]

I suspect that having the capability would be good, but this really comes down to how we implement Sync 2.0 wrt FxA and its ToS in the client. And the privacy and legal teams probably care.

Over to magic manager Toby! :D

Comment 2

[Toby Elliott [:telliott]]

This is almost entirely a legal question, so I'm adding Jishnu. I suspect we should make a habit of it.

Tokenserver already has this capability built in (since we needed it for AITC), so there should be minimal-none server work. The client code can probably be grabbed from there.

Comment 3

[Ryan Kelly [:rfkelly]]

Unblocking the sync2.0-protocol-docs metabug, since I can't think of anything more useful to say than the "go look at tokenserver access flow docs" that is already there.

Comment 4

[Toby Elliott [:telliott]]

ToS acceptance is handled as a blanket part of FxA, so this is addressed.