668
edits
Identity/Verified Email Protocol/Latest: Difference between revisions
Identity/Verified Email Protocol/Latest (view source)
Revision as of 01:10, 2 November 2011
, 2 November 2011→Relying Party Flow
| Line 77: | Line 77: | ||
* If Alice chooses to cancel the transaction, <tt>gotAssertion</tt> is invoked with no parameters. | * 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. | * If Alice chooses to authenticate using one of her email addresses, <tt>gotAssertion</tt> is invoked with a single parameter, an Identity Assertion. | ||
* <tt>example.com</tt> should take this assertion and pass it back to its server. This can be accomplished with an AJAX request. For example, using jQuery: | |||
function gotAssertion(assertion) { | |||
if (!assertion) { | |||
alert('you canceled login!'); | |||
} else { | |||
$.post("/verifyAssertion", {assertion: assertion}, afterVerifyAssertion); | |||
} | |||
} | |||
== User-Agent Compliance == | == User-Agent Compliance == | ||