Are you planning to evolve this into something that manages identity-attached services, or is this just a hard-coded SSO-style thing?
For example, will I be able to answer the questions: • Which services does this user use with her FxA? (Presumably not all of the ones we offer…) • Which services could this user use? • Which token server does this user use to sync? and make the assertion: • Here’s the token server this uses for Sync 1.5. ? Or are you expecting that to itself be a service that’s an attached API? Endlessly hoping for the trifecta of identity management, service management, device management, -R On 8 Oct 2014, at 5:20 PM, Chris Karlof <[email protected]> wrote: > Yeah, something seemed missing: > > https://developer.mozilla.org/en-US/docs/Mozilla/APIs_attached_to_Firefox_Accounts > > -chris > > > On Oct 8, 2014, at 5:17 PM, Chris Karlof <[email protected]> wrote: > >> This is a WIP. Currently, the only API associated with FxA is the FxA >> profile service, but going forward, I anticipate this is how we will >> authenticate access to Mozilla APIs providing FxA user data or otherwise >> require authentication. >> >> Thoughts, questions? >> >> -chris >> > > _______________________________________________ > Dev-fxacct mailing list > [email protected] > https://mail.mozilla.org/listinfo/dev-fxacct
_______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
