Live data from Hacker News

The SSO Wall of Shame

sso.tax

41–44 of 44 posts

Re: The SSO Wall of Shame

#41
post #35
post #16

Earlier quoted context omitted.

There are a couple of other free options I'm aware of. * FusionAuth has a community edition which is free as long as you host it yourself and comply with the license ( https://fusionauth.io/license-faq#3 ). Free as in beer, at least. (Full disclosure, I work for FusionAuth.) Here's our SSO guide: https://fusionauth.io/docs/v1/tech/guides/single-sign-on * If you want a SaaS solution, Cognito is an option, as is Azure…

> The source code for the fusionauth-app bundle and all closed source libraries owned by FusionAuth cannot be decompiled or reverse engineered. This prevents companies from forking FusionAuth and creating their own solution to sell to their customers (i.e. like Amazon has done with ElasticSearch). Is AGPL or one of those new licenses like the BSL not sufficient to prevent this sort of thing?

I'm not sure why we went with our own license, but we did.

The full legalese is here: https://fusionauth.io/license

Re: The SSO Wall of Shame

#42

Is there an easy way to get started with SSO on a SAAS app? (Without paying per user on Okta/Auth0) I'm currently using Firebase which supports sign-in with Microsoft, but not sure if that's technically the same as SSO.

Please do give SAML Jackson a try, we've married SAML with OAuth2.0 - https://github.com/boxyhq/jackson

Re: The SSO Wall of Shame

#43

Is there an easy way to get started with SSO on a SAAS app? (Without paying per user on Okta/Auth0) I'm currently using Firebase which supports sign-in with Microsoft, but not sure if that's technically the same as SSO.

You might be a great candidate for Keycloak.

Looks great, thanks for the suggestion

Re: The SSO Wall of Shame

#44

As a normal home user, I avoid SSO like the plague. I don't want to wake up one day to find that Google has decided I'm a spammer or something, and turned off my Google account, thus disabling my login to 30 other sites.

Likewise, for personal stuff I prefer to create an account per site rather than login with a provider that could block me.

However at work it's a pain managing users on paid services, and getting access can sometimes take days. SSO makes a lot more sense for corporate accounts.

Post reply on HN