If this has to take off, even with browsers providing an easier UI to create and manage client side certificates, two things would be important to avoid confusing users and a lot of &quot;&lt;insert browser name here&gt; is crap and broke my login&quot; messages:<p>1.  Easy sync of the certificates across devices (as mentioned in the article, allow the user to choose which ones to sync). Most (non-tech-savvy) people still don&#x27;t use password managers, and instead remember or write down passwords. You have to make it easy for these people to use multiple devices without having to jump through hoops. Even private keys protected by a passphrase&#x2F;password add one more barrier (assuming each user has a separate OS account and is logged in). How would a user setup a new device with a previously setup client certificate? What fallback mechanisms (other than form based user&#x2F;password auth) would be required for cases where a user wants to use a public computer or a shared computer account?<p>2. Handling the reissue of client side certificates for the expiring&#x2F;expired ones along with revocation (if&#x2F;when necessary). I believe this is a huge topic by itself on both the usability and security fronts. What would be the sweet spots for the expiry enforced for a particular site? Six months? One year? Two years? Ten years? Considering that most users in the current form based authentication scheme rarely change passwords, the convenience, or rather, the reduction in annoyance to end users, should be an important consideration.<p>I have seen client side certificates used in corporate environments where the management of these is easier, but even in those cases I have always seen alternatives like form based authentication available, along with other things like NTLM, etc.<p>Please comment&#x2F;inform if any&#x2F;what prior work has been done in these areas (I&#x27;m sure many people must have thought about these).