Multi-tenant SAML in an afternoon (using SSOReady) – tylerrussell.dev
tldr; I took SSOReady up on their marketing tagline of “SAML in an afternoon”. Overall, it was a positive experience and despite not quite having a production-ready deployment in an afternoon, I think their tagline is a fair approximation of effort.
Enterprise SSO logins are a weird dictomony. Implementing something like OIDC or SAML isn’t necessarily hard but there is always a debate of whether to implement it internally or use a vendor. There never feels like there is a simple answer.
Your framework might support it, but you probably need to know more about SAML than you want to know. If you already started with an IdP, congratulations, you might be in luck. If it’s a vendored-IdP, for a not-so-small fee, you can add OIDC or SAML on a per-customer basis. The industry average seems to be between $50-$100 per customer.
If you started with the username/password implementation that came with your framework like most startups do, then now you have a decision to make. Do you tag on a SAML implementation on your application or make the full switch to an IdP and pay the cost of migration (and possibly throwing away a bunch of code).
