668
edits
Identity/Verified Email Protocol/Latest: Difference between revisions
Jump to navigation
Jump to search
Identity/Verified Email Protocol/Latest (view source)
Revision as of 01:07, 2 November 2011
, 2 November 2011→Relying Party Flow
| Line 71: | Line 71: | ||
Consider a web site, <tt>http://example.com</tt>, receiving a visit from a user. This web site wishes to obtain the user's verified email address using the Verified Email Protocol. The user in question, for the purposes of this description, is Alice. Alice owns two email addresses, <tt>alice@homedomain</tt> and <tt>alice@workdomain</tt>. | Consider a web site, <tt>http://example.com</tt>, receiving a visit from a user. This web site wishes to obtain the user's verified email address using the Verified Email Protocol. The user in question, for the purposes of this description, is Alice. Alice owns two email addresses, <tt>alice@homedomain</tt> and <tt>alice@workdomain</tt>. | ||
# <tt>example.com</tt> presents a login button with a JavaScript click handler. | # <tt>example.com</tt> presents a login button with a JavaScript click handler. | ||
# when Alice clicks the login button, <tt>example.com</tt>'s click handler invokes | # when Alice clicks the login button, <tt>example.com</tt>'s click handler invokes | ||
| Line 77: | Line 77: | ||
where <tt>gotAssertion</tt> is a previously defined function. | where <tt>gotAssertion</tt> is a previously defined function. | ||
# Alice is presented with a user-agent dialog that lets her select which email to present to <tt>example.com</tt>. | |||
# If Alice chooses to cancel the transaction, <tt>gotAssertion</tt> is invoked with no parameters. | |||
# If Alice chooses to authenticate using one of her email addresses, <tt>gotAssertion</tt> is invoked with a single parameter, an Identity Assertion. | |||
== User-Agent Compliance == | == User-Agent Compliance == | ||