<?xml version="1.0" encoding="UTF-8" standalone="yes"?><oembed><version><![CDATA[1.0]]></version><provider_name><![CDATA[Occasionally Coherent]]></provider_name><provider_url><![CDATA[http://blog.bimajority.org]]></provider_url><author_name><![CDATA[Garrett Wollman]]></author_name><author_url><![CDATA[https://blog.bimajority.org/author/garrettwollman/]]></author_url><title><![CDATA[An update on the HTTPS client certificate&nbsp;issue]]></title><type><![CDATA[link]]></type><html><![CDATA[<p>Attention conservation notice: If you&#8217;re here for the food, you can skip this post &#8212; maybe another recipe post coming towards the end of the month.</p>
<p>I wrote a while back about moves in the browser world to <a href="https://blog.bimajority.org/2015/10/05/in-defense-of-client-certificates/">deprecate client certificate authentication</a>.  Things have moved on a bit, and at work today I did a presentation and community discussion about the issue and what we&#8217;re going to do about it.  (Summary: in the near term, we&#8217;ll be adopting OpenID Connect to centralize the actual authentication piece of this, which will allow us to swap in other mechanisms &#8212; or delegate the actual authentication to someone else &#8212; as alternatives become available.)  <a href="http://tig.csail.mit.edu/wiki/pub/TIG/FutureOfClientAuthentication/May_2_OIDC_presentation.key.pdf">My slides are available</a> although (because of the room it was held in) neither the talk itself nor the discussion afterward were recorded.</p>
]]></html></oembed>