Identity/Architecture/SignIntoBrowser: Difference between revisions
(Created page with "= Use Cases = Check out the Feature Page. Brief version: Alice signs into her Firefox with Persona credentials, and her Firefox is i...") |
No edit summary |
||
| Line 1: | Line 1: | ||
= Use Cases = | == Use Cases == | ||
Check out the [[Identity/Features/Sign_into_the_browser|Feature Page]]. | Check out the [[Identity/Features/Sign_into_the_browser|Feature Page]]. | ||
| Line 5: | Line 5: | ||
Brief version: Alice signs into her Firefox with Persona credentials, and her Firefox is immediately customized with her theme, bookmarks, passwords, history, add-ons, apps, and identities. | Brief version: Alice signs into her Firefox with Persona credentials, and her Firefox is immediately customized with her theme, bookmarks, passwords, history, add-ons, apps, and identities. | ||
= Components = | == Goals == | ||
=== Reusable but Flexible Identity === | |||
If Alice logs into her browser as <tt>alice@example.com</tt>, she should be able to immediately use that identity to log into web sites. She should not be limited to that identity alone, however, and she should have her other preferred identities immediately at her disposal without having to retype them on each device. | |||
=== Pluggable Services === | |||
Alice should be able to use the services of her choice, e.g. store her bookmarks with Google, her passwords and apps with Mozilla, and her contacts with her cell phone operator. | |||
=== Pluggable Browsing Context Provider === | |||
Alice should be able to select the server that performs the initial signin-to-the-browser authentication and setup of her preferred services. E.g., this may be a corporate directory server. | |||
== Components == | |||
=== Browsing Context Provider (BCP) === | |||
=== ID-attached Services === | |||
=== User-Agent === | |||
== Flow == | |||
Revision as of 00:16, 21 April 2012
Use Cases
Check out the Feature Page.
Brief version: Alice signs into her Firefox with Persona credentials, and her Firefox is immediately customized with her theme, bookmarks, passwords, history, add-ons, apps, and identities.
Goals
Reusable but Flexible Identity
If Alice logs into her browser as alice@example.com, she should be able to immediately use that identity to log into web sites. She should not be limited to that identity alone, however, and she should have her other preferred identities immediately at her disposal without having to retype them on each device.
Pluggable Services
Alice should be able to use the services of her choice, e.g. store her bookmarks with Google, her passwords and apps with Mozilla, and her contacts with her cell phone operator.
Pluggable Browsing Context Provider
Alice should be able to select the server that performs the initial signin-to-the-browser authentication and setup of her preferred services. E.g., this may be a corporate directory server.