668
edits
Identity/BrowserID: Difference between revisions
Jump to navigation
Jump to search
→API
(→API) |
|||
| Line 185: | Line 185: | ||
* A <tt>login</tt> event if the user chose to log in. This event MUST include the Backed Identity Assertion in the <tt>assertion</tt> property. | * A <tt>login</tt> event if the user chose to log in. This event MUST include the Backed Identity Assertion in the <tt>assertion</tt> property. | ||
XXX: should we provide error information if it's not just a user cancel? | |||
==== Provisioning ==== | |||
The User Agent should support a provisioning workflow when a user wants to authenticate with a new email address. A provisioning workflow is initiated with some context: | |||
* the email address being provisioned | |||
* information about the security status of the session (user's own computer, shared computer, public computer, ...) | |||
During a provisioning action, the User Agent MUST support the following API calls: | |||
<tt>navigator.id.beginProvisioning(object callback)</tt> | <tt>navigator.id.beginProvisioning(object callback)</tt> | ||
The callback function SHOULD accept parameters <tt>email</tt> and <tt>cert_duration_s</tt>. | The callback function SHOULD expect the callback function to accept parameters <tt>email</tt> and <tt>cert_duration_s</tt>. | ||
In response to this call, the user agent should invoke the callback | |||
<tt>navigator.id.genKeyPair(object callback);</tt> | <tt>navigator.id.genKeyPair(object callback);</tt> | ||