668
edits
Changes
→Provisioning
* the email address being provisioned
* information about the security status of the session (user's own computer, shared computer, public computer, ...)
* whether the authentication workflow has been invoked yet (initially <tt>false</tt>).
During a provisioning action, the User Agent MUST support the following API calls:
<tt>navigator.id.raiseProvisioningFailure(string reason);</tt>
The User Agent MUST interrupt this provisioning workflow and . If the context indicates that the authentication workflow has already been invoked, then the User Agent SHOULD return with a from this workflow indicating failure for to authenticate the user. If the context indicates that the authentication workflow has NOT already been invoked, then the User Agent SHOULD begin the given <tt>reason</tt>Authentication Workflow (described below).
WebIDL:
