On 1/09/2015 10:25, Nicholas Alexander wrote: > Hi folks, > > Me, rfkelly, zaach, and markh had a discussion about keeping a device's > FxA login state in sync with the fxa-content-server. By "device", I > mean a Firefox -- Desktop, iOS, Android. > > We discussed two main use cases, both after a user signs in to Sync in > the browser. The first case is that they use a third party oauth relier > (like Pocket): we want to give a smooth, password-less flow when > possible. The device knows that the user is signed in, even if browser > state (cookies, localStorage) that might tell accounts.firefox.com > <http://accounts.firefox.com> that the user is signed in is not > present. The second case is that a user is signed in and wants to go to > accounts.firefox.com/settings <http://accounts.firefox.com/settings> and > interact, but again the browser state is missing. > > We discussed a number of aspects of this; sorry, I didn't take notes. > We ended up with the following avenue to pursue: > > * a message exchange from fxa-content-server to device and back. This > exchange can target WebChannels only, since older devices won't > participate. This exchange cannot be dependent on the context query > parameter, since an oauth relier (like Pocket) will not produce that > parameter.
Thanks Nick! I don't have any more details to add, but I do want to propose that we give this exchange a concrete name to make it easier to talk about the feature and any spin-off work. Perhaps "Device Handshake"? Ryan _______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
