SSO should be table stakes

Re:SSO should be table stakes by rubixdude on Monday June 20, 2022 @12:24PM (#31812217)

I wonder if the author discussed this with his support team? The reason my company charges for SSO is then increased support cost.

If everyone used Okta, no problem. But then you get an Enterpise customer who’s using their own home grown SSO solution an we get to spend weeks debugging login issues.

[ Parent | on HN ]

Re:SSO should be table stakes by ShakataGaNai on Monday June 20, 2022 @06:39PM (#31817130)

Most sites have a preset for the major identity providers, Okta, Microsoft, OneLogin, etc. The ones who want to be nice will also have a generic "SAML" option allowing connections to just about anything - but that's when the home grown solution pain shows up.

But you can support just 5ish SAML IDP's and get a large majority of the market and have effectively no ongoing support issues because its really well known (and well documented) how to set them up.

[ Parent | on HN ]

Re:SSO should be table stakes by r00k on Monday June 20, 2022 @12:27PM (#31812252)

I sit next to our support "team" pretty frequently :)

We've had a couple painful SSO integrations (when they were home-grown, as you correctly point out), but we've pretty much got the rough edges sanded down now. I don't think we've had a tough one in a while.

It helped to publish some short docs on it: https://tuple.app/sso_setup

[ Parent | on HN ]