Open ryanfeeley opened 11 years ago
Hrm. Feels out-of-scope to me. Persona auth's yr id federatedly and hands-off to RP. Am I missing something?
+1 to close.
@r0bl0rd It's a feature we'll eventually need to consider adding or risk losing the convenience wars with the rest of the NASCAR. Social networks provide the personal information that is often required by RPS (e.g. name, birthdate, city) and users despise retyping this information (especially on mobile). Beyond that, an opportunity exists to create a standard for data interchange between the RP and, for example, financial information providers who do not want to rely on FB for any part of their business transactions.
This also feels out of scope to me. I particularly like how Ozten put it in this thread: http://thread.gmane.org/gmane.comp.mozilla.identity.devel/5400/focus=5408
I think this is Persona. The API, identity picker, and protocol. The other projects are Identity projects with their own branding and user experience. Persona is scoped to authentication between a persona and their software. Nothing more.
To flesh things out: I have a pretty minimalist view of Persona, and this user story feels like it falls beyond that scope.
Lloyd's post on "What is Persona?" ends with:
Persona is an easy way to sign in that enables you to use your existing email account. It's an open technology on the path to standardization.
This story helps users "sign up," but it feels pretty distinct from helping them "sign in." Personal / medical / financial information don't feel intrinsically linked to an existing email account of mine, either. But I have a super minimal view. I'd like to defer to Product: @lloyd and @r0bl0rd.
For what it's worth, PICL and/or Google's requestAutocomplete() feel like better homes for this. To me.
Again probably in the realm of PiCL @skinny97214, but the user should be able to share non-browser related information, like shipping address, employer name, etc. which is store elsewhere, without having to type it in.