Hi All,
The latest production push of tokenserver brought a subtle change in
behaviour that might impact folks testing our various staging and dev
environments. It now *only* accepts assertions issued by the production
Firefox Accounts server, rather than accepting BrowserID assertions from
any valid issuer.
Normal users should not see any difference due to this change, but it
will be visible if e.g. you've previously tested the dev FxA server in
combination with the prod Tokenserver.
The details of the change are discussed here:
https://github.com/mozilla-services/tokenserver/issues/50
To test the entire login+sync flow from the FxA dev or staging
environments, please use the staging tokenserver instance at:
https://token.state.mozaws.net
This will happily accept assertions from the following issuers:
api.accounts.firefox.com
api-accounts.stage.mozaws.net
api-accounts-dev.stage.mozaws.net
mockmyid.com
Cheers,
Ryan
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
