Closed Bug 1105438 Opened 11 years ago Closed 11 years ago

Native FxA needs to side-step the sign-in button page for login

Categories

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

Avenir
x86
macOS
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: muffinresearch, Assigned: muffinresearch)

References

Details

Persona required us to do a click for the login. FxA doesn't. The web-based flow already bypasses these views for login and reset. Native FxA should too. Once this is done these views should be removed entirely. Bear in mind there's parts of the existing tests that use this flow that are going to look for those pages so those will need updating too. Looks like the reset side might have already been solved here in bug 1103103
Note this requires the enableNativeFxA setting to be true to be seen.
Assignee: nobody → scolville
Priority: -- → P3
Re-purposing this bug for login only as it will be easier to test. Will file a separate bug for reset as that's a separate issue. LOGIN button STR: You can repro seeing the old persona login button from in-app payments tester. * Use FFOS 2.1 * Without being logged in to FxA * Open the in-app payment tester app and point it at marketplace-dev * Click refresh JWT * This will show the button that needs to be clicked to continue logging in.
Summary: Native FxA needs to side-step the sign-in pages for login and reset. → Native FxA needs to side-step the sign-in button page for login
After testing the branch I'd setup for side-stepping the login click with Charles on -dev. I found that the indentity code that runs for NAtive FxA still requires the login to happen based on user input. As a result of that we aren't going to be able to remove this page because the request must happen on user input. Marking as invalid and filing a new bug to update the UX of that page instead. It's worth noting that due to the login from Marketplace the only time users will hit this is for login for in-app payments and resets.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.