Hacker News new | past | comments | ask | show | jobs | submit login

> OIDC or SAML should not be "taxed" extra.

But it costs extra. That cost is passed on to the consumer.

The major hurdle is that it's expensive!

Take a typical small business SaaS - providing SSO instead of standard passwords can take more time and effort to purchase or develop and to roll out than the actual SaaS software.

Okay, lets say you buy SSO: offloading to a service is going to cost a minimum of an extra $20/month/user.

Building it? That's going to take months of developer time, not to mention that this is a high-touch/high-feedback feature, which is going to eat up the service employees time.

And then the rollout, which almost always needs a month of external consultants getting everything working correctly.

I'm doing a small SaaS, $15/user/month; if anyone has any good recommendations that aren't going to to cost me a quarter of my current sale price, I'm all ears.

Even if it's DIY, as long as I don't burn a month of dev-time just for integration/deployment.




There likely is an off the shelf OIDC SP provider you can use for the actual "hard parts".

If you already use something like "Sign in with {Google,Facebook,Twitter,Apple}" you are already doing part of it.

I have built several products now with OIDC support for authentication (not authorization) and it has never taken more than a day or two to wire it up.


My advice would be to wait until a big enough customer is willing to pay through the nose for it. You’re “lucky” in that you charge per user so it’s easy to model into your pricing :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: