[wldlyinaccurate]

I just finished adding SSO to the (very small) SaaS company that I work for, and this page gives me mixed feelings.

Yeah, SSO is a security feature and you expect to get security for free. But SSO is not free for us as the service provider. We pay a vendor (Auth0) a decent amount of money to handle all the hard stuff. We also have to manually set up SSO for each of our customers who want it, which can take anywhere between 10 minutes to several hours depending on whether the customer has set up SSO before. For these reasons, we charge an annual fee for SSO on top of the regular subscription fee. We're just not big enough to absorb the cost.

[scarface74]

I agree. We are B2B company and while we include the price of SSO with the contract, we also only work with “whales”.

It takes us about two or three hours of coordinating with our client to configure SSO and that’s if they only use it for authentication. If they use it for authorization also where we base their permissions on claims they send us - as oppose to an admin in their side configuring their users - it’s a lot more coordination.

We host our own Ping Federate instances.

[kasey_junk]

In my experience SSO is one of the most expensive features to build but worse than that it’s one of the most expensive to operate.

Your system becomes hard dependent on a piece of infrastructure outside of your control, frequently provided by some bad IT vendor. Failures on their side are always blamed on you & you spend tons of resources debugging their problems.

I’ll buy that SSO is a core feature but that doesn’t change the economics of it. It needs to require higher prices.