749072 - [meta] Implement sign in to the browser and sign out of Firefox Mobile

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: General, defect)

Description

[Asa Dotzler [:asa]]

By signing in to the browser, the user connects to a Persona account, which provides a discovery point for id-attached services.

See https://wiki.mozilla.org/Identity/Features/Sign_into_the_browser and https://wiki.mozilla.org/Kilimanjaro/ProductDraft#All_your_devices_recognize_you_and_enable_access_to_your_ID-attached_services

Comment 1

[Chris Lee [:clee]]

Can we file a separate bug for the discovery part? This should be narrowly about login/logout.

Comment 2

[Mark Finkle (:mfinkle) (use needinfo?)]

Technically, this bug is a meta bug. So let's add new bugs as we need them and link back to this bug.

Comment 3

[Asa Dotzler [:asa]]

Per recent Product Team discussions, we are dropping sign into the browser from kK90. Sign into Persona in content will be sufficient for K9O

Comment 4

[Jason Smith [:jsmith]]

(In reply to Asa Dotzler [:asa] from comment #3)
> Per recent Product Team discussions, we are dropping sign into the browser
> from kK90. Sign into Persona in content will be sufficient for K9O

(In reply to Asa Dotzler [:asa] from comment #2)
> Per recent Product Team discussions, we are dropping sign into the browser
> from kK90. Sign into Persona in content will be sufficient for K9O

I'm a bit nervous about the implications this could have on the user experience for AITC, as I've had discussions with Anant while testing AITC desktop where discussion points came up with something like:

"Issue will likely be better solved when sign into browser comes down the pipeline"

Anant - What are your thoughts on this? I'm a bit nervous about this being deprioritized in how it affects the UX of AITC. We should talk about this at Tuesday's AITC meeting to evaluate the impacts of the deprioritization here and address if we agree or disagree with the k9o -.

Comment 5

[Matthew N. [:MattN]]

UX Mockup: http://people.mozilla.com/~zfang/SignInMobile/Mobile.html

Comment 6

[Caspy7]

(In reply to Matthew N. [:MattN] from comment #5)
> UX Mockup: http://people.mozilla.com/~zfang/SignInMobile/Mobile.html

Does that page need further changes to the browser UI to protect against spoofing (like we do with about:addons)?

Forgive me if it's a silly question. I do not have an Android phone so I may be missing something.
Can a website not concoct a similar screen for the second step in the sign in for existing users?

Comment 7

[BMO Automation]

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.