Identity/Features/Web-based Verified Email Client - Revision history

Thunder at 03:31, 5 February 2012

2012-02-05T03:31:20Z

← Older revision		Revision as of 03:31, 5 February 2012
Line 1:		Line 1:
	{{FeatureStatus		{{FeatureStatus
	\|Feature name=Web-based Verified Email Client		\|Feature name=Web-based Verified Email Client
	\|Feature stage=~~Shelved~~		\|Feature stage=Complete
	\|Feature status note=Scoping new work after VEP changes.		\|Feature status note=Scoping new work after VEP changes.
	}}		}}

Curtisk at 02:42, 7 January 2012

2012-01-07T02:42:30Z

← Older revision		Revision as of 02:42, 7 January 2012
Line 119:		Line 119:
	}}		}}
	{{FeatureTeamStatus		{{FeatureTeamStatus
			\|Feature security status=sec-review-unnecessary
	\|Feature security notes=2-Dec-2011: notified project canceled/shelved, removing security tags and closing out feature page per discussion with Rob Miller. Project superseded by BrowserID		\|Feature security notes=2-Dec-2011: notified project canceled/shelved, removing security tags and closing out feature page per discussion with Rob Miller. Project superseded by BrowserID
	}}		}}

Curtisk at 19:17, 2 December 2011

2011-12-02T19:17:26Z

← Older revision		Revision as of 19:17, 2 December 2011
Line 1:		Line 1:
	{{FeatureStatus		{{FeatureStatus
	\|Feature name=Web-based Verified Email Client		\|Feature name=Web-based Verified Email Client
	\|Feature stage=~~Definition~~		\|Feature stage=Shelved
	~~\|Feature health=OK~~
	\|Feature status note=Scoping new work after VEP changes.		\|Feature status note=Scoping new work after VEP changes.
	}}		}}
Line 120:		Line 119:
	}}		}}
	{{FeatureTeamStatus		{{FeatureTeamStatus
	\|Feature security ~~status~~=~~sec~~-~~review~~-~~needed~~		\|Feature security notes=2-Dec-2011: notified project canceled/shelved, removing security tags and closing out feature page per discussion with Rob Miller. Project superseded by BrowserID
	}}		}}

Curtisk at 14:02, 21 July 2011

2011-07-21T14:02:15Z

← Older revision		Revision as of 14:02, 21 July 2011
Line 119:		Line 119:
	\|Feature engineering team=Services		\|Feature engineering team=Services
	}}		}}
	{{FeatureTeamStatus}}		{{FeatureTeamStatus
			\|Feature security status=sec-review-needed
			}}

Twalker at 01:18, 20 July 2011

2011-07-20T01:18:24Z

← Older revision		Revision as of 01:18, 20 July 2011
Line 11:		Line 11:
	\|Feature security lead=Michael Coates		\|Feature security lead=Michael Coates
	\|Feature privacy lead=Sid Stamm		\|Feature privacy lead=Sid Stamm
	\|Feature qa lead=~~Tracy Walker~~		\|Feature qa lead=James Bonacci
	\|Feature ux lead=Chris Howse		\|Feature ux lead=Chris Howse
	}}		}}
Line 97:		Line 97:
	** including HTTP Auth, forms-based sign-in, OpenID, OAuth, etc.		** including HTTP Auth, forms-based sign-in, OpenID, OAuth, etc.
	* Support for other profile information		* Support for other profile information

	\|Feature functional spec==== API Docs ===		\|Feature functional spec==== API Docs ===
	* [[Identity/Verified Email Protocol\|Verified Email Protocol]]		* [[Identity/Verified Email Protocol\|Verified Email Protocol]]
Line 104:		Line 103:
	Obsolete?		Obsolete?
	* [[MozillaID/InternalSpec\|Client API]]		* [[MozillaID/InternalSpec\|Client API]]

	\|Feature ux design=[[File:Registration.png\|200px\|thumb\|left\|Registration (i2)]]		\|Feature ux design=[[File:Registration.png\|200px\|thumb\|left\|Registration (i2)]]
	[[File:Sign-In-Single-Email.png\|200px\|thumb\|left\|Single email (i2)]]		[[File:Sign-In-Single-Email.png\|200px\|thumb\|left\|Single email (i2)]]
Line 113:		Line 111:
	Older mockups:		Older mockups:
	* [[media:WebLogin.jpg\|Login popup flow (i1)]]		* [[media:WebLogin.jpg\|Login popup flow (i1)]]

	\|Feature qa review=Basic Identity items [https://wiki.mozilla.org/Identity/QA test plan]		\|Feature qa review=Basic Identity items [https://wiki.mozilla.org/Identity/QA test plan]
	}}		}}

Dria at 18:22, 14 July 2011

2011-07-14T18:22:30Z

← Older revision	Revision as of 18:22, 14 July 2011
Line 1:	Line 1:
		{{FeatureStatus
		\|Feature name=Web-based Verified Email Client
		\|Feature stage=Definition
		\|Feature health=OK
		\|Feature status note=Scoping new work after VEP changes.
		}}
		{{FeatureTeam
		\|Feature product manager=Dan Mills
		\|Feature feature manager=Dan Mills
		\|Feature lead engineer=Rob Miller
		\|Feature security lead=Michael Coates
		\|Feature privacy lead=Sid Stamm
		\|Feature qa lead=Tracy Walker
		\|Feature ux lead=Chris Howse
		}}
		{{FeaturePageBody
		\|Feature overview=Pure HTML client of the Verified Email Service.

		Related features:
		* [[../Verified Email Service\|Verified Email Service]]
		* [[../Firefox-native Verified Email Client\|Firefox-native Verified Email Client]]
		* [[../Verified Email Service Admin Interface\|Verified Email Service Admin Interface]]

		Goals:
		* Implement the JS API for sites to support Verified Email
		* Not to interfere when native browser support is present
		* Directly interface with the Mozilla Verified Email service for all functionality
		* Support Verified Email on current-generation browsers: Firefox 4, IE 8, Chrome 10, Safari 5, Opera
		\|Feature users and use cases=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 on the SaladFans site, and when he clicks on it a Mozilla ID pop-up dialog comes up telling him that the site is asking for a verified email address to sign-in. Mark hasn't used Mozilla ID before, so he clicks the "register" button.

		Mark now types in his email address, and chooses a password for his account. After he's done, Mozilla ID tells him that a verification message has been sent to his email, and he 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, and Mark is now signed into SaladFans.com!

		Key Points:
		* Easy set-up from scratch
		* All HTML flow, works on a variety of browsers
		* Flow centered around verified email disclosure
		\|Feature requirements=<table width="100%" cellpadding="3">
		<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> Core VEP client implementation (can handshake w/ server register an email, generate keys, receive a cert, generate assertion; no UI, no cert refresh) </td><td> 664598 </td><td> -
		</tr>
		<tr>
		<td> Relying party wrapper implementation (can handle getVerifiedEmail call and interact w/ core VEP client in a popup window; still no UI nor cert refresh) </td><td> 664597 </td><td> -
		</tr>
		<tr>
		<td> Identity authority wrapper implementation (can handler registerVerifiedEmail and registerVerifiedEmailCertificate calls and can interact w/ core VEP client in parent window, still no UI nor cert refresh) </td><td> 669455 </td><td> -
		</tr>
		<tr>
		<td> UI interaction through account creation / login / release of one email address (most UI will be generated by the server) </td><td> 664594 </td><td> -
		</tr>
		<tr>
		<td> Email selection UI (mostly generated by UA) and integration into VEP process </td><td> 664599 </td><td> - </td>
		</tr>
		<tr>
		<td> Certificate refresh, successful only </td><td> 668620 </td><td> - </td>
		</tr>
		<tr>
		<td> Certificate refresh w/ failure </td><td> 668625 </td><td> - </td>
		</tr>
		<tr>
		<td colspan="3"> ========= OLDER (OBSOLETE?) MILESTONES BELOW ========== </td>
		</tr>
		<tr>
		<td> Relying party API </td><td> - </td><td> - </td>
		</tr>
		<tr>
		<td> Sign-in pop-up </td><td> - </td><td> - </td>
		</tr>
		<tr>
		<td> Email disclosure pop-up </td><td> - </td><td> - </td>
		</tr>
		<tr>
		<td> Email verification pop-up </td><td> - </td><td> - </td>
		</tr>
		<tr>
		<td> Account creation pop-up </td><td> - </td><td> - </td>
		</tr>
		<tr>
		<td> Account creation UX polish[1] </td><td> - </td><td> - </td>
		</tr>
		<tr>
		<td> HTML client popups support multiple emails </td><td> - </td><td> - </td>
		</tr>
		<tr>
		<td> HTML client allows adding a new email to an existing account </td><td> - </td><td> - </td>
		</tr>
		</table>

		[1] ''e.g., password strength meter, pop-up auto-closes upon email verification''
		\|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

		\|Feature functional spec==== API Docs ===
		* [[Identity/Verified Email Protocol\|Verified Email Protocol]]
		* [[Services/Identity/HTML_Client\|HTML client design notes]]

		Obsolete?
		* [[MozillaID/InternalSpec\|Client API]]

		\|Feature ux design=[[File:Registration.png\|200px\|thumb\|left\|Registration (i2)]]
		[[File:Sign-In-Single-Email.png\|200px\|thumb\|left\|Single email (i2)]]
		[[File:Sign-In-and-Site-Identity.png\|200px\|thumb\|left\|Multi email (i2)]]

		<br clear="all"/>

		Older mockups:
		* [[media:WebLogin.jpg\|Login popup flow (i1)]]

		\|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}}

Dria: Blanked the page

2011-07-14T18:15:32Z

Blanked the page

Show changes

Rafrombrc: /* Release Requirements */

2011-07-05T21:14:12Z

Release Requirements

← Older revision		Revision as of 21:14, 5 July 2011
Line 45:		Line 45:
	\|-		\|-
	\| Relying party wrapper implementation (can handle getVerifiedEmail call and interact w/ core VEP client in a popup window; still no UI nor cert refresh) \|\| 664597 \|\| -		\| Relying party wrapper implementation (can handle getVerifiedEmail call and interact w/ core VEP client in a popup window; still no UI nor cert refresh) \|\| 664597 \|\| -
			\|-
			\| Identity authority wrapper implementation (can handler registerVerifiedEmail and registerVerifiedEmailCertificate calls and can interact w/ core VEP client in parent window, still no UI nor cert refresh) \|\| 669455 \|\| -
	\|-		\|-
	\| UI interaction through account creation / login / release of one email address (most UI will be generated by the server) \|\| 664594 \|\| -		\| UI interaction through account creation / login / release of one email address (most UI will be generated by the server) \|\| 664594 \|\| -

Rafrombrc: /* Release Requirements */

2011-06-30T20:32:32Z

Release Requirements

← Older revision		Revision as of 20:32, 30 June 2011
Line 54:		Line 54:
	\| Certificate refresh w/ failure \|\| 668625 \|\| -		\| Certificate refresh w/ failure \|\| 668625 \|\| -
	\|-		\|-
	\| ~~====~~========= OLDER (OBSOLETE?) MILESTONES BELOW ~~===~~==========		\| ========= OLDER (OBSOLETE?) MILESTONES BELOW ==========
	\|-		\|-
	\| Relying party API \|\| - \|\| -		\| Relying party API \|\| - \|\| -

Rafrombrc: /* Release Requirements */

2011-06-30T20:28:30Z

Release Requirements

← Older revision		Revision as of 20:28, 30 June 2011
Line 42:		Line 42:
	\| style="background-color: #efefef;"\| '''Status'''		\| style="background-color: #efefef;"\| '''Status'''
	\|-		\|-
	\| Core VEP client implementation (can handshake w/ server register an email, generate keys, receive a cert, generate assertion; no UI, no cert refresh) \|\| - \|\| -		\| Core VEP client implementation (can handshake w/ server register an email, generate keys, receive a cert, generate assertion; no UI, no cert refresh) \|\| 664598 \|\| -
	\|-		\|-
	\| Relying party wrapper implementation (can handle getVerifiedEmail call and interact w/ core VEP client in a popup window; still no UI nor cert refresh) \|\| - \|\| -		\| Relying party wrapper implementation (can handle getVerifiedEmail call and interact w/ core VEP client in a popup window; still no UI nor cert refresh) \|\| 664597 \|\| -
	\|-		\|-
	\| UI interaction through account creation / login / release of one email address (most UI will be generated by the server) \|\| - \|\| -		\| UI interaction through account creation / login / release of one email address (most UI will be generated by the server) \|\| 664594 \|\| -
	\|-		\|-
	\| Email selection UI (mostly generated by UA) and integration into VEP process \|\| - \|\| -		\| Email selection UI (mostly generated by UA) and integration into VEP process \|\| 664599 \|\| -
	\|-		\|-
	\| Certificate refresh, successful only \|\| - \|\| -		\| Certificate refresh, successful only \|\| 668620 \|\| -
	\|-		\|-
	\| Certificate refresh w/ failure \|\| - \|\| -		\| Certificate refresh w/ failure \|\| 668625 \|\| -
	\|-		\|-
	\| ============= OLDER (OBSOLETE?) MILESTONES BELOW =============		\| ============= OLDER (OBSOLETE?) MILESTONES BELOW =============