668
edits
Identity/BrowserID: Difference between revisions
Jump to navigation
Jump to search
→Certifying Users
| Line 356: | Line 356: | ||
with <tt>gotPublicKey</tt> a function that accepts a JWK-string-formatted public-key. | with <tt>gotPublicKey</tt> a function that accepts a JWK-string-formatted public-key. | ||
The domain's JavaScript SHOULD then send this JWK string to the domain's backend server. The domain's backend server SHOULD certify this key along with the email address provided to its <tt>provisionEmailFunction</tt> function, and an expiration date at least 1 minutes in the future. The backend server SHOULD NOT issue a certificate valid longer than 24 hours. The domain's backend server SHOULD then deliver | The domain's JavaScript SHOULD then send this JWK string to the domain's backend server. The domain's backend server SHOULD certify this key along with the email address provided to its <tt>provisionEmailFunction</tt> function, and an expiration date at least 1 minutes in the future. The backend server SHOULD NOT issue a certificate valid longer than 24 hours. The domain's backend server SHOULD then deliver an Identity Certificate back to its JavaScript context. The domain's JavaScript MUST finally call: | ||
navigator.id.registerCertificate(certificate); | navigator.id.registerCertificate(certificate); | ||
with the | with the Identity Certificate string. | ||
== Assertion Verification == | == Assertion Verification == | ||