1088063 - Create a WebCrypto based API for managing TLS client certificates

Status: RESOLVED WONTFIX

(Core :: DOM: Web Crypto, task, P5)

Description

[Richard Barnes [:rbarnes]]

Web sites used to be able to create and import client certificates using <keygen>, generateCRMFRequest(), and importUserCertificate().  But we removed those functions.
https://developer.mozilla.org/en-US/docs/Archive/Mozilla/JavaScript_crypto 

So there is no way to manage client certificates "in band" today.  You have to go to the certificate manager in the preferences and manually install a cert.

WebCrypto gives us a sensible way to replace the above functions, in that <keygen> can be replaced with crypto.subtle.generateKey(), and the cert generation things can be replaced with JS/XHR.  The only missing piece is the import.

We should expose a simple API that allows JS to set and inspect the private key and certificate that should be used for TLS to a given HTTPS origin (the origin of the JS).  It seems to me that this could be functionally quite similar to document.cookie -- something like document.tlsClient.certificate and document.tlsClient.privateKey

Comment 1

[Darkspirit]

An additional function to close a [client certificate authenticated] tls session (Logout) would be helpful here, so that users don't have to restart Firefox every time.

Comment 2

[Darkspirit]

As Chrome 57 will deprecate <keygen> ( https://www.chromestatus.com/features/5716060992962560 ) this should get a focus for business needs and WebID. Please consider to adjust the prioritization.

Comment 3

[Markus Schraeder]

We also use productive the keygen and import possibility on firefox... How is the alternative way to do this now, if you realy want to sadly remove this feature?

Comment 4

[Markus Schraeder]

We are using keygen, cause its the only way on firefox to import certificates a way the users is able to: -> Because firefox is not using the certificate store of windows.

Please donnot remove this feature untils there is a other way to access the firefox certificate store without installing a program or using the absurd gui for importing a pks12!

Comment 6

[Markus Schraeder]

As you can read on 

https://github.com/w3c/webauthn/issues/1027

the webautn is NOT a replacement for client certification or the authentication of users.

You always need to buy hardware to be able to use webauthn, a hardware free implementation is missing.

Please do not stop supporting keygen until webauthn has the possibility to use public keys without any hardware given!

Comment 7

[Anna Weine]

I don't think that WebCrypto team is interested in doing this, so I close the patch until any update