After a user logs in to her Firefox Account, the browser obtains a sessionToken and signed public key from the Firefox Account Server. The browser uses the signed public key to generate BrowserID assertions for authenticating itself to the Sync 2.0. For our Milestone 1, this signed public key might have a long validity period, but it is intended to be shortish and periodically re-signed using the sessionToken.

Ryan Kelly has stood up a Sync 2.0 token server that accepts BrowserID assertions for dev purposes at http://auth.oldsync.dev.lcip.org/ Details: https://mail.mozilla.org/pipermail/sync-dev/2013-August/000392.html

Next steps: 1) Get an account on rkelly's Sync 2.0 token server 2) Create a static assertion blob for that account. 3) Add an xpcshell test file to services/services/sync/tests/unit/ that: i. Passes the assertion to the token server and receives the token ii. Passes the token to the storage server at http://db1.oldsync.dev.lcip.org/

Bug #912188 is a more specific bug for this.

Yep. Makes sense.