Hi All, This week we'll be rolling FxA train-42 to production, with the following highlights:
* Users can now opt to use Gravatar for their profile picture. * Users can now explicitly set a blank display-name. * The first-run flow now receives notifications of important events such as page load, email verification, and sign-in success. * Our metrics infrastructure now consumes Google Analytics parameters such as "utm_campaign" and routes them back to GA on the server side. This allows us to provide campaign metrics to the Growth Team without including any third-party javascript on our pages. * Sampled client-side metrics are now correlated across email sending events; for example, if we log client metrics on the sign-up page then we now ensure that metrics are also logged on the corresponding verification page, even if it's opened in a different browser. * Login requests that pass the "service" parameter can specify it in the query string in addition to the request body. * The implicit OAuth flow can now specify a TTL for its access tokens, to make them shorter-lived than the server-set default TTL. * The user's password verification hash is now never read from the database; instead we pass the candidate hash into the database for verification. As always, you can dig into the details through the CHANGELOG files in each individual repo: https://github.com/mozilla/fxa-profile-server/blob/master/CHANGELOG.md https://github.com/mozilla/fxa-content-server/blob/master/CHANGELOG.md https://github.com/mozilla/fxa-oauth-server/blob/master/CHANGELOG.md https://github.com/mozilla/fxa-auth-server/blob/master/CHANGELOG Cheers, Ryan _______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
