Hi All,

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


On the Backend:

* Uploaded profile pictures are now available in "small", "default",
  and "large" variants.

* We now track account lifecycle events in the database, for future
  publishing to a dedicated notification service.

* OAuth client management APIs are exposed in production, on a separate
  privileged admin port.  This will enable use of our command-line
  client management tool in production.

* Account lockout now tracks failed login attempts over a longer period.

* The code now builds and runs on ARM platforms (including Raspberry Pi)

* Several bugfixes and improvements to our logging setup.


On the Frontend:

* Reliers can now iframe the standard oauth redirect flow, rather than
  having to support a separate "iframe broker" flow.

* Change event notifications are now broadcast to all listening channels
  in the browser.  For example, if you change your profile in one tab,
  other tabs will receive a `profile:image:change` event.

* Any catastrophic errors during client-side startup are now displayed
  correctly in the Firefox error console.


As always, you can dig into the details through the CHANGELOG files in
each individual repo:

   https://github.com/mozilla/fxa-auth-server/blob/master/CHANGELOG
   https://github.com/mozilla/fxa-auth-db-mysql/blob/master/CHANGELOG
   https://github.com/mozilla/fxa-oauth-server/blob/master/CHANGELOG.md
   https://github.com/mozilla/fxa-profile-server/blob/master/CHANGELOG.md
   https://github.com/mozilla/fxa-customs-server/blob/master/CHANGELOG
   https://github.com/mozilla/fxa-content-server/blob/master/CHANGELOG.md


  Cheers,

    Ryan
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct

Reply via email to