Identity/Verified Email Protocol/Latest: Difference between revisions

Identity/Verified Email Protocol/Latest (view source)

Revision as of 00:35, 2 November 2011

462 bytes added , 2 November 2011

→‎Browser-Level API

BenAdida

668

edits

@@ Line 69: / Line 69: @@
 <tt>navigator.id.getVerifiedEmail(object options, function callback);</tt>
-The Relying Party MAY call the navigator.id.getVerifiedEmail method when it wishes to request that the User Agent generate an identity assertion as soon as it can. The User Agent SHOULD immediately seek to generate an Identity Assertion, prompting the user if needed, and call the provided callback with an identity assertion or null in case of failure.
+The Relying Party MAY call the navigator.id.getVerifiedEmail method when it wishes to request that the User Agent generate an identity assertion as soon as it can. The User Agent SHOULD immediately seek to generate an Identity Assertion, prompting the user if it deems it necessary, and call the provided callback with an identity assertion or null in case the user chooses not to log in.
+FIXME: should we provide error information if it's not just a user cancel?
 <tt>navigator.id.beginProvisioning(object callback)</tt>
@@ Line 75: / Line 77: @@
 The callback function SHOULD accept parameters <tt>email</tt> and <tt>cert_duration_s</tt>.
-<tt>navigator.id.genKeyPair(function(pubkey) { });</tt>
+<tt>navigator.id.genKeyPair(object callback);</tt>
+The callback function SHOULD accept parameter <tt>pubkey</tt>, a serialized public-key string as per the above public-key spec.
 <tt>navigator.id.registerCertificate(certificate);</tt>
+The certificate parameter MUST be a valid serialized certificate, as per the above spec.
 <tt>navigator.id.raiseProvisioningFailure(string reason);</tt>
+The reason parameter MUST be a string that can be reported to the user regarding the reason why a certificate failed to be provisioned.
 WebIDL: