+loop-services-dev
+dev-fxacct

Here’s a list of the tracking bugs for FxA/Loop that I know of:

Changes to Desktop client to support new FxA Oauth integration API:
https://bugzilla.mozilla.org/show_bug.cgi?id=979845

Changes to Loop server to support FxA Oauth:
https://bugzilla.mozilla.org/show_bug.cgi?id=1041814

PR to FxA Web content to support these flows:
https://github.com/mozilla/fxa-content-server/pull/1423

Issue for Loop server to get FxA Oauth credentials:
https://github.com/mozilla/fxa-oauth-server/issues/110

And yes, FxA team is on target for integrating with loop for Fx34. 

-chris



On Jul 21, 2014, at 2:00 PM, Shell Escalante <[email protected]> wrote:

> +Chris
> 
> Hi Tauni,
> Hi Tarek,
> 
> Do you know if there is a bug for tracking the server work for FxA for 
> desktop (maybe in github) that I can point to from a new bugzilla tracking 
> bug?
> 
> Or did we just miss creating one in any area (highly likely with all the 
> moving parts) - so we need to create and track now.  
> 
> ----- Forwarded Message -----
> From: "Shell Escalante" <[email protected]>
> To: "Edwin Wong" <[email protected]>, "Matthew Noorenberghe" 
> <[email protected]>, [email protected]
> Cc: [email protected], [email protected], [email protected], 
> [email protected], [email protected], [email protected], 
> [email protected], [email protected], [email protected]
> Sent: Monday, July 21, 2014 1:43:41 PM
> Subject: Re: FxA Loop support
> 
> Agreed - our emails crossed in being sent :)  Let's see if this sounds right:
> 
> Per Maire talking with Chris Karloff: 
> **MattN (Desktop) is going to finish off FxA once Vlad is finished. Vlad 
> should be done this week with FxA on desktop. 
>     (Matt please correct if you had other conflicting priorities)
> **the server work to add FxA for desktop is additional beyond the FxA for 
> mobile, but minimal (per ckarloff).
>     We could not find a bug for the server work - so it needs to be added as 
> server work needed. 
> 
> So now I need to talk with Tarek and test to see if the bug fits in their 
> second sprint Fx34 - with a goal of testing and deploying for production by 
> 9/1
> 
> Does that sound right to everyone?  
> 
> ----- Original Message -----
> From: "Edwin Wong" <[email protected]>
> To: [email protected], [email protected], [email protected], 
> [email protected], [email protected], [email protected], 
> [email protected], [email protected], [email protected], [email protected]
> Cc: "Shell Escalante" <[email protected]>
> Sent: Monday, July 21, 2014 1:33:10 PM
> Subject: FxA Loop support
> 
> 
> 
> It was mentioned in this mornings meeting that Firefox Accounts support is 
> NOT officially committed for Fx34.  The documented plan and rest of the Loop 
> client team are currently under the assumption that it IS committed for Fx34. 
>  I know that we have a fxa-loop-oauth-desktop prototype in place and it may 
> land in time, commitment or not.
> 
> However, we should all be on the same page here.  
> 
> -edwin
> 
> ---------
> 
> From: Shell Escalante <[email protected]>
> Subject: Re: Question: FxA for Loop onFx34
> Date: July 21, 2014 at 1:16:24 PM PDT
> 
> Hi Tauni, 
> Hi Edwin, 
> 
> The MOBILE Loop client has FxA authentication capabilities with Bug 1019564 - 
> Integrate with the FxA verifier.  FxA authN is being tested with the early 
> version of the mobile loop client.
> 
> On the Fx DESKTOP side the target is to have authentication in Loop for Fx34:
> Bug 979845 - [meta] Desktop Client needs ability to authenticate via FxA to 
> the server
> Though the decision was to use oAuth to do the authentication, so slightly 
> less integrated that full FxA integration - 
> https://etherpad.mozilla.org/MWt7hqDivW
> 
> Let me know if there are still questions.
> 
> Cheers,
> Shell

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

Reply via email to