Changes

Jump to: navigation, search

CloudServices/Roadmaps/Identity

979 bytes removed, 22:24, 2 March 2011
→‎Use Cases
= Use Cases =
note: these use;First-cases are out of date, will be updated soon. ;Part one: Mark signs in Mark is a Firefox user. He has a laptop and an iPhone, and he uses Firefox Sync to access his bookmarks from his phone.run experience
Mark gets a tip from a friend about SaladFans.com, a place to review and share your favorite salad bars. Mark visits the site and is eager to contribute his own reviews as well as connecting with friends to find out which salad bars they like.
Mark sees a "sign in" button which is styled with on the Mozilla color SaladFans site, and logo. Mark hasn't used Mozilla ID before, so when he clicks the button Mark's browser pops up an introduction message that points him to the identity area on the toolbar, and tells him that his Sync ID has been automatically upgraded to it a Mozilla ID (so it uses the same password). After dismissing the introduction pop-up dialog, the identity area pops comes up a doorhanger notification telling him that SaladFans.com the site is asking for his a verified email addressto sign--is it OK to give it to them? Mark says OK and the page refreshes, mark is now signed in! Summary:* Easy set-up on Firefox + Sync machines* Chrome-enhanced experience on Firefox* Attribute exchange of basic info (email) ;Part two: Mark on the go A few days later, . Mark meets George at a party and they start talking about salad bars--it turns out that they are both salad lovers! George hasn't been to SaladFans.com used Mozilla ID before, so Mark wants to show it to him. Mark uses Firefox Home to quickly find SaladFans.com from his list of recently visited sites and opens it in Mobile Safari. Mark wants to sign in to show George one of his draft salad bar reviews he has been working on. He finds clicks the familiar "sign inregister" button styled with the Mozilla logo, and taps on it. Because he's on Mobile Safari, Mark gets redirected to the Mozilla ID website where he can sign in.
Mark taps now types in his email address , and chooses a passwordfor his account. After he's done, Mozilla ID tells him that a verification message has been sent to his email, and he gets redirected back needs to click on a link there before proceeding. Mark checks his email and clicks on the link in the message Mozilla ID sent him. The link opens up a new pop-up replacing the previous one, which welcomes him to Mozilla ID and asks him if it's OK to disclose the email address to SaladFans.com. Mark clicks OK, the dialog closes, SaladFans.com reloads, where he's and Mark is now signed in with his Mozilla IDinto SaladFans.com!
Summary:
* Works Easy set-up from scratch* All HTML flow, works on any modern browsera variety of browsers* HTML-based baseline experienceFlow centered around verified email disclosure
;Part three (aspirational): Mark finds his friends onlineEnhanced Firefox experience
''Note: this last This use-case is not reflected in part of the plan/requirements below - . It's here to help guide our API design choices, since it's food for thought as we think of critical that sites don't need to do anything special to trigger the futureenhanced chrome flow.''
Mark wants to share his salad bar reviews with his friends. He knows some of his friends are already using SaladFansAnne is a Firefox user.comShe has an iPhone too, but he hasn't connected with them on the site yetand uses Firefox Sync to get to her bookmarks from her phone.
Mark clicks While browsing the "friends" button on SaladFans.com and Firefox prompts him with Web, Anne sees a doorhanger notification bar in Firefox asking her to tell him that SaladFans.com is requesting his friends list--but that unfortunately it's empty! He can connect verify the email address she uses to another service to add his friends howeversign into Firefox Sync. Mark Anne decides to do thatgo ahead, Firefox opens up clicks a page that lists possible accounts he can connect button to his Mozilla ID. Mark has send a lot of friends on his Google address-bookverification message, so he clicks the Google buttonand is told to check her inbox for a message.
Mozilla ID directs him to Google's site where Mark needs to verify that he wants to connect his Google account to his Mozilla IDAnne finds the message in her inbox and clicks the link. After Mark confirms, he goes She is taken back to SaladFansFirefox and a message thanks her for verifying the email address.com and Firefox asks him to confirm again also tells her that he wants she can now use her verified email address to share his friends list with SaladFans.com. Mark says OK, and Mozilla works with SaladFans.com to disclose his contacts which are already using the sign into any supported Web site, without disclosing the ones that aren'tany extra passwords.
Now While talking to her friend Mark, Anne learns about SaladFans.com can ask Mozilla ID for updates . Excited to his friends listtry it out, she browses to the site on her desktop, and that way when Mark adds a new friend she clicks the "sign in" button, Firefox asks her if it's OK to his contact listdisclose her verified email address with SaladFans.com. Anne clicks OK, they will automatically be connected on SaladFans.comrefreshes and she is now signed in!
Summary:
* Basis for sharing infrastructureSame site API triggers enhanced chrome dialogs in Firefox* Mozilla ID remembers auth decisions for ongoing disclosure (app permissions)Firefox reuses Sync credentials* Firefox can verify the email proactively before first-use
= Requirements =
Thunder
946
edits
Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/288267"

Navigation menu