<story><title>Beer Drinkers Guide to SAML</title><url>https://duo.com/blog/the-beer-drinkers-guide-to-saml</url></story><parent_chain></parent_chain><comment><author>lvh</author><text>The biggest problem with SAML is probably XML-DSig. The spec is ridiculously complex, but unfortunately the implementations are no better. You&amp;#x27;re de facto either using libxmlsec1 or the Java stdlib. libxmlsec1 is (anecdotally) a terrifying mess of C that most SAML integration libraries desperately want you to run in-process with your server.&lt;p&gt;There&amp;#x27;s a totally palatable mini-SAML within SAML waiting to come out. It already exists informally: it&amp;#x27;s whatever GSuite and Okta&amp;#x27;s default metadata.xml will give you, and it summarizes to &amp;quot;one signature, on the outside, no encryption&amp;quot;.&lt;p&gt;You kind of need to do SAML, though, unless you don&amp;#x27;t care about selling to companies at all. Smaller companies may or may not be able to do OIDC, but pretty much everyone can do SAML. You just want to have someone else be responsible for the SAML laundromat part (that is: ingesting gross SAML from the Internet and translating it to a friendly consistent format, which doesn&amp;#x27;t necessarily have to be SAML too). For all its flaws, Cognito fits that bill, as does Okta.</text></comment>
<story><title>Beer Drinkers Guide to SAML</title><url>https://duo.com/blog/the-beer-drinkers-guide-to-saml</url></story><parent_chain></parent_chain><comment><author>mirekrusin</author><text>Great article but if I wanted to explain it to somebody in one sentence I&amp;#x27;d say &amp;quot;It&amp;#x27;s like sign-in with google, but for enterprises&amp;quot;, by &amp;quot;enterprises&amp;quot; i mean &amp;quot;more shit&amp;quot; - xml&amp;#x2F;soap&amp;#x2F;overcomplicated kind of shit.</text></comment>