On 2/02/2016 06:03, Andrew McKay wrote:
> Just to update you on timeline, we are aiming for turning this on with
> our AMO push on Feb 11th and burning down the remaining issues.

Great, thanks for the update Andy!

The curious can try it out in dev, complete with Firefox Accounts
integration, at:

  https://addons-dev.allizom.org/en-US/firefox/

> I don't
> think this will affect the FxA team much, apart from we'll need some
> config setup before then:
> 
> https://github.com/mozilla/olympia/issues/1565

If you haven't kicked off this process already, please file a bug like
the following and cc myself, :jrgm and :ckolos:

  https://bugzilla.mozilla.org/show_bug.cgi?id=1225620

> If there's any questions, feel free to ping me.

No questions, but this is a great opportunity to sync up on some details
of the FxA integration:

1) For logins where you know you're migrating an existing user, please
pass "migration=amo" in the query parameters when kicking off the oauth
dance.  This will give us the ability to show a bit of extra messaging
to guide those users, and described in:

  https://github.com/mozilla/fxa-content-server/issues/3399

2) Since AMO is a trusted relier, you don't get the standard oauth
permission prompt asking whether the user wants to share their profile
data.  If you'd like to trigger it explicitly to get the UX shown in
this issue:

  https://github.com/mozilla/fxa-content-server/issues/2477

Then please pass "prompt=consent" as a query parameter when kicking off
the oauth dance.  We don't have the code for showing that view in
production yet, but this will ensure we can switch it on for you when
it's ready.

(Since you're requesting "profile" scope, you already have the power to
fetch display-name and avatar from the fxa-profile-server; the only
change would be to make us explicitly prompt the user to confirm or deny
this ability)

3) When signing up for a new Firefox Account through this process, only
the original tab completes the oauth flow by redirecting back to AMO.
If I close the original tab and the open the verification link in a new
tab, I'll get dead-ended on a page that says "you're ready to use AMO".

This seems OK to me, but I hadn't seen it discussed explicitly.  Please
let us know if you want to make any tweaks to that flow, to have e.g.
both the original *and* verification tabs redirect back to AMO.

Looking forward to seeing this go live!


  Cheers,

    Ryan

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

Reply via email to