Hi All,

Next week we'll be rolling FxA train-59 to production, with the
following highlights:

* Email status checks now accept a "reason" parameter, which the
  client can use to indicate the reason for polling the endpoint.
  We currently accept a value of "reason=push" to track metrics
  on how well our push notifications are performing.

* Any auth-server endpoints now accept a "metricsContext" object
  as part of the request body, which can be used to provide contextual
  information such as entrypoint, service name, and utm_* campaign
  parameters.

* The oauth basket proxy now supports the /subscribe_sms route, which
  allows you to SMS yourself an install link for Firefox for Android.
  UX work to take advantage of this is ongoing.

* Our password reset emails have been refreshed to match the changes
  to the reset flow shipped in train-58.

* There's much improved handling of deleted accounts on the /force_auth
  screen; previously this situation would produce a dead end.

* Query parameters are now validated against an explicit declarative
  schema, powered by a new general-purpose module called "VAT" [1].

* We now use the <meta name="referrer"> tag to ensure any outgoing
  referer heads contain only "accounts.firefox.com" rather than the
  full page URL with query string etc.

* We no longer show un-actionable error messages when polling for
  account confirmation.


As usual, you can dig into all the details and smaller changes in the
changelog:

  https://github.com/mozilla/fxa-content-server/blob/master/CHANGELOG.md
  https://github.com/mozilla/fxa-auth-server/blob/master/CHANGELOG.md
  https://github.com/mozilla/fxa-basket-proxy/blob/master/CHANGELOG.md



  Cheers,

    Ryan


[1] https://github.com/shane-tomlinson/vat
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct

Reply via email to