canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906
edits
Identity/Features/Verified Email Service: Difference between revisions
Jump to navigation
Jump to search
m
Identity/Features/Verified Email Service (view source)
Revision as of 16:56, 14 July 2011
, 14 July 2011no edit summary
m (clearing in prep for migration to new feature page format) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{FeatureStatus | |||
|Feature name=Verified Email Service | |||
|Feature stage=Definition | |||
|Feature health=Blocked | |||
|Feature status note=Scoping new work after VEP changes. | |||
}} | |||
{{FeatureTeam | |||
|Feature product manager=Dan Mills | |||
|Feature feature manager=Dan Mills | |||
|Feature lead engineer=JR Conlin | |||
|Feature security lead=Michael Coates | |||
|Feature privacy lead=Sid Stamm | |||
|Feature qa lead=Tracy Walker | |||
}} | |||
{{FeaturePageBody | |||
|Feature overview=Backend service that implements a "Secondary Authority", allowing sites to implement the [Identity/Verified Email Protocol|Verified Email Protocol] on their sites and users to sign into those sites by using e-mail addresses verified by Mozilla. | |||
This service leverages our existing Firefox Sync accounts, turning them into more general Firefox Accounts. | |||
Goals: | |||
* Implement a "Secondary Authority" -- a service which issues Mozilla-signed identity assertions to other sites. These assertions are for email addresses we have verified as belonging to the user | |||
* Users can verify any email address they wish, and any number of them | |||
* Implement a "Secondary Verifier" -- a service able to verify identity assertions for other sites via a server-to-server API | |||
* Implement all APIs necessary to build the HTML and Firefox-native clients | |||
Related features: | |||
* [[../Web-based Verified Email Client|Web-based Verified Email Client]] | |||
* [[../Firefox-native Verified Email Client|Firefox-native Verified Email Client]] | |||
* [[../Verified Email Service Admin Interface|Verified Email Service Admin Interface]] | |||
|Feature requirements=<table class="fullwidth-table"> | |||
<tr> | |||
<td style="background-color: #efefef;">'''Item'''</td> | |||
<td style="background-color: #efefef;">'''Bug'''</td> | |||
<td style="background-color: #efefef;">'''Status'''</td> | |||
</tr> | |||
<tr> | |||
<td> R3.1 Service uses Firefox Sync IDs as its auth backend </td><td> - </td><td> - </td> | |||
</tr> | |||
<tr> | |||
<td> R3.2 registerVerifiedEmail / registerVerifiedEmailCertificate support </td><td> - </td><td> - </td> | |||
</tr> | |||
<tr> | |||
<td> R3.3 API for clients to create new accounts (without necessarily provisioning Sync) </td><td> - </td><td> - </td> | |||
</tr> | |||
<tr> | |||
<td> R3.4 API for clients to add/remove email addresses to/from an existing account </td><td> - </td><td> - </td> | |||
</tr> | |||
<tr> | |||
<td> R3.5 API for clients to send/re-send verification emails </td><td> - </td><td> - </td> | |||
</tr> | |||
<tr> | |||
<td> R3.6 API for clients to list verified/pending emails </td><td> - </td><td> - </td> | |||
</tr> | |||
<tr> | |||
<td> R3.7 Service implements APIs for verifying identity assertions (for sites) </td><td> - </td><td> - </td> | |||
</tr> | |||
</table> | |||
|Feature non-goals=* Integrating with/implementing non-Verified Email auth protocols | |||
** including HTTP Auth, forms-based sign-in, OpenID, OAuth, etc. | |||
* Support for other profile information (we'll do this potentially in the future) | |||
|Feature functional spec=* [[Identity/Verified Email Protocol|Verified Email Protocol]] | |||
|Feature qa review=* Basic Identity items [https://wiki.mozilla.org/Identity/QA test plan] | |||
}} | |||
{{FeatureInfo | |||
|Feature priority=P1 | |||
|Feature roadmap=Mozilla Identity | |||
|Feature list=Services | |||
|Feature engineering team=Services | |||
}} | |||
{{FeatureTeamStatus}} | |||