668
edits
Identity/BrowserID: Difference between revisions
Jump to navigation
Jump to search
→Primary Authority Compliance
| Line 308: | Line 308: | ||
* declare support and parameters for BrowserID | * declare support and parameters for BrowserID | ||
* provide a user-authentication web flow | * provide a user-authentication web flow | ||
* provide a user-certification web flow | * provide a user-key-certification web flow | ||
=== BrowserID Support Document === | === BrowserID Support Document === | ||
| Line 339: | Line 339: | ||
=== Certifying Users === | === Certifying Users === | ||
A BrowserID-compliant domain MUST provider user-key-certification at the URI referenced by the <tt>provisioning</tt> field in its published BrowserID support document, as follows: | |||
* deliver HTML and JavaScript at that URI, which it can expect to be evaluated in a standard user-agent IFRAME. | |||
* determine, without any user-facing content, the user's state of authentication with the domain. The domain MAY use cookies or localStorage to make this determination. | |||
* in JavaScript, call: | |||
navigator.id.beginProvisioning(provisionEmailFunction); | |||
where <tt>provisionEmailFunction</tt> is a function that accepts an email address as parameter. | |||
== Assertion Verification == | == Assertion Verification == | ||