668
edits
Identity/BrowserID: Difference between revisions
Jump to navigation
Jump to search
→User-Agent Compliance
| Line 279: | Line 279: | ||
} | } | ||
}; | }; | ||
=== Authenticating === | |||
The User Agent MUST support an authentication workflow when a user wants to certify a new email address but has failed the provisioning workflow. An authentication workflow is initiated with some context: | |||
* the email address which requires authentication | |||
During an authentication workflow, the User Agent MUST support the following API calls: | |||
navigator.id.beginAuthentication(object callback); | |||
The User Agent SHOULD expect a callback function as parameter to this API call. | |||
When this function is invoked, the User Agent MUST invoke the callback function, passing to it the context's email address as parameter. | |||
navigator.id.completeAuthentication(); | |||
When this function is invoked, the User Agent MUST return to its provisioning workflow, retrieving the appropriate context for that provisioning workflow, with the added flag <tt>authenticationPerformed = true</tt>. | |||
navigator.id.raiseAuthenticationFailure(string reason); | |||
When this function is invoked, the User Agent MUST return to its provisioning workflow and proceed with the failure case. | |||
== Primary Authority Compliance == | == Primary Authority Compliance == | ||