<story><title>SAML: A Technical Primer</title><url>https://ssoready.com/docs/saml/saml-technical-primer</url></story><parent_chain><item><author>pmontra</author><text>Surprisingly the page doesn&amp;#x27;t explain the meaning of SAML. It&amp;#x27;s Security Assertion Markup Language &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Security_Assertion_Markup_Language&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Security_Assertion_Markup_Lang...&lt;/a&gt;</text></item></parent_chain><comment><author>nocman</author><text>Oh, I thought it stood for:&lt;p&gt;&amp;quot;Suffering A Massive Lot&amp;quot; - jk&lt;p&gt;Let&amp;#x27;s just say my interaction with managing websites that used SAML was less than pleasant.</text></comment>
<story><title>SAML: A Technical Primer</title><url>https://ssoready.com/docs/saml/saml-technical-primer</url></story><parent_chain><item><author>pmontra</author><text>Surprisingly the page doesn&amp;#x27;t explain the meaning of SAML. It&amp;#x27;s Security Assertion Markup Language &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Security_Assertion_Markup_Language&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Security_Assertion_Markup_Lang...&lt;/a&gt;</text></item></parent_chain><comment><author>Terretta</author><text>(S)uggest (A)lternative (M)odern (L)ogin: OIDC&amp;#x2F;Oauth2  ?&lt;p&gt;The &amp;quot;Continue with&amp;quot; buttons that include Microsoft, Google, and Apple, tend to pick up most SMBs without SAML SSO headaches on either side.&lt;p&gt;Like so:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.xsplit.com&amp;#x2F;user&amp;#x2F;auth&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.xsplit.com&amp;#x2F;user&amp;#x2F;auth&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;id.atlassian.com&amp;#x2F;login&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;id.atlassian.com&amp;#x2F;login&lt;/a&gt;&lt;p&gt;Use an email domain restriction, and you have by and large SSO; the user can only log into your SaaS if the user is an active account at that company.&lt;p&gt;Storing user passwords yourself is a liability, indirect or direct: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.reuters.com&amp;#x2F;technology&amp;#x2F;eu-privacy-regulator-fines-meta-91-million-euros-over-password-storage-2024-09-27&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.reuters.com&amp;#x2F;technology&amp;#x2F;eu-privacy-regulator-fine...&lt;/a&gt;</text></comment>