Identity/Features/Firefox-native Verified Email Client

Feature	Status	ETA	Owner
In-browser sign-in UI	Finalizing APIs and UX mockups. Development starting up.	TBD	Dan Mills

Summary

Ability to sign into web sites using Verified Email, integrated with our ID service (see MozillaID).

Team

Who's working on this?

• Feature Manager: Dan Mills
• Lead Developer: David Dahl
• Product Manager: Dan Mills
• QA: Tracy Walker
• UX: Alex Faaborg
• Security: Curtis Koenig
• Privacy: Sid Stamm

Release Requirements

Content APIs in place for web sites to:

• Request a verified email from the browser
• Be proactively given a verified email
• Advertise active/passive sign-in user sessions and sign-out method

Browser UI in place to:

• Create a Firefox Account
• Sign into a Firefox Account
• Add an email address to a Firefox Account, and verify it
• Sign into a site by disclosing an email, whether the process is started from chrome or content
• Display active session(s) with the site, and sign-out

Next Steps

• Finalize UX mockups [Alex Faaborg]
• Finalize session API [Team-wide]
• Create test plan [?]
• Security review
• Engineering work (see bugs linked below) [David Dahl]

Related Bugs & Dependencies

• Tracking bug
  • Tracking bug: email disclosure APIs
  • Tracking bug: Firefox account & email verification UI
  • Tracking bug: Session discovery & chrome UI

Designs

API docs:

• Verified Email Protocol
• Client API

Future API spec (for reference):

• Verified Email Protocol (Labs)

Mockups:

• Are We Pretty Yet? - Account Manager
• HTML client mockups

Use Cases

Everyone loves use cases, so you should provide them if you can (and where it makes sense). The Channel Switcher Feature Page has some good examples.

Test Plans

Any and all test plans and strategies. Either inline or linked to.

Goals

• Provide a convenient way for users to sign-in and sign-out of web sites by using their verified email address
• Anchor signed-in status & functionality to a consistent location in browser chrome
• Integrate with the Firefox Account, the same account used for Firefox Sync
• Provide an on-ramp to a fully distributed verified email system down the road (see Labs' Verified Email protocol)

Non-Goals

• Integrating with/implementing non-Verified Email auth protocols
  • including HTTP Auth, forms-based sign-in, OpenID, OAuth, etc.
• Multiple accounts per-site (plus fast-user switching)
• Expanding "sign into the browser" role to allow multiple user support, profile switching support, master password support
• Integrating account information into site-prefs
• Implementing fully de-centralized Verified Email support

Legend (remove if you like)

	Healthy: feature is progressing as expected.
	Blocked: feature is currently blocked.
	At Risk: feature is at risk of missing its targeted release.
ETA	Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.