Connectivity: wifi SIM used: Gaia/device: Flame/2.1 steps to reproduce: 1. Tester is not signed in 2. Launch marketplace payments-alt app 3. Search for :paid 4. Start the purchase of an app 5. Sign in using fxA expected behavior: After user signs in, Enter PIN screen loads actual behavior: After user signs in, the webpay screen with 'Sign in' button loads, clicking that loads the fxa screen again. See attached video.

Not a blocker. I think the issue here is the best way to share state between webpay and zamboni. window.localStorage.getItem('0::user') Will give us the user from commonplace. How secure and how much we can use that is the question, if we can use it, we should and then eliminate the double login.

Hrm.. I disagree. Making the user log in twice makes the user flow almost unusable. So, even though the payment flow would work if the user logged in twice, I doubt there are many users out there willing to log in twice to purchase an app. I would at least make this P1 major. Please reconsider.

Passing through the email in JWT for the marketplace: https://github.com/mozilla/zamboni/pull/2664

Establishing webpay session based on marketplace JWT: https://github.com/mozilla/webpay/commit/438a83938e3b7970a98672e4a0b098e7b3bea0bf Skipping login prompt when session exists: https://github.com/mozilla/spartacus/commit/cf822eebde63814cb3179d9d504711e02d97e54f

This doesn't happen anymore. The user needs to sign in only once.