2 ms·
One problem is that keygen is either deprecated or not supported. So you have to create the client cert on the server, then have the user download it (including
by z3t4 11y ago
One problem is that keygen is either deprecated or not supported. So you have to create the client cert on the server, then have the user download it (including private key). Or the client has to create a signing request and then upload it to the server, and then download the certificate.
Once that is done though, client certificates works pretty well, the browser will pop up a "what certificate to use" dialog when entering the web site. And the server (nginx) will send all the details like name, city etc to the web-server application.
Another problem vs passwords, is that the user has to copy or download the certificate to each computer device. And just like passwords, you need to have a process for identifying the user in case he lose the certificate/key.
- finnn 11y agoI've used the HTML5 <keygen> element in Chrome and Firefox with great results. Chrome (on a Chromebook) even stored the generate key in the TPM on the device
- Arnavion 11y agoI believe z3t4's point is that the element is deprecated after HTML5, so you can't rely on it working forever, or gaining adoption in new browsers that don't already have it.