1106106 - [Spartacus] Understand what differences there are between persona and Native FxA

Status: RESOLVED WONTFIX

(Marketplace Graveyard :: Payments/Refunds, defect, P4)

Description

[Stuart Colville [:muffinresearch]]

The persona code has been re-purposed with changes to mozId instead of navigator.id for the native FxA flow. 

Is the API otherwise identical? If it is we can close this bug, if not let's understand the differences and amend the code + tests accordingly.

Assiging to Allen who know the most about this for clarification.

Comment 1

[Allen Short [:ashort]]

The primary differences are not supporting unverified emails and putting the user email in a different field (the regular 'email' field being used for the fxa uid). I've updated the code to be in line with zamboni's native fxa support in bug 1108650.

Comment 2

[Stuart Colville [:muffinresearch]]

The mock login for Persona stubbyid.js is being used to stand in for nativeFxA now. But persona has one big difference which is that it managed its own state. 

What I need to know is what changes do we need to make to stubbyid.js so that it is representative of the native API? Also we need to be sure that the code that worked for Persona *is* handling things correctly with respect to the native FxA API.

Comment 3

[Stuart Colville [:muffinresearch]]

Presumably the best output of this bug would be to file any other bugs we need to deal with detailing what we need to change.

Comment 4

[Andy McKay]

Based on the recently announced future plans for the Marketplace to remove payments, closing these bugs.