On 6/14/19 7:02 AM, Henri Sivonen wrote:
Thanks for the removal. Do we have enterprise Web developer-facing
documentation on 1) how TLS client cert enrollment should work now or
2) if there is no in-browser client cert enrollment path anymore, what
concretely should be used instead?
For what it's worth, the one case I am familiar with (MIT) has a native
app you run to manage your keystore for non-Firefox browsers (presumably
by changing the OS keystore) and uses <keygen> in Firefox. See
http://kb.mit.edu/confluence/display/istcontrib/Certificates+Landing+Page#CertificatesLandingPage-GetCertificates
How viable is it to extend such a native app to munge the Firefox
keystore? If it is, we should probably document it...
-Boris
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform