11–20 of 44 posts
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.
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.
If you want something more permanant Keycloak is probably your best bet. I'm not aware of any other truly free ones
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.
If you are just testing, grab an AzureAD development account. If you want something more permanant Keycloak is probably your best bet. I'm not aware of any other truly free ones
* 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 AD B2C. They have good free tiers, as long as you don't want SAML integration (for Cognito, you're charged after 50 users).
* If you want to run your own, you could conceivably cobble something together on whatever tech stack you run. Ruby on rails, java/spring, django/python all have libraries which can be used to build OIDC servers. Then it's a question of setting up the sessions correctly. Here's an example I found via googling: https://tushartuteja.medium.com/a-simple-single-sign-on-sso-...
* As the parent comment mentioned, Keycloak is an option as well.
> The right way to think of the "SSO tax" (where companies charge extra for security features) is "You are being offered a dual use product backed by a strong engineering team for far less than it would otherwise cost, with sophisticated enterprises picking up the slack."
https://twitter.com/patio11/status/1481293027331440640
Further down the thread:
> SSO is a segmentation lever, and a particularly powerful one because (as @tqbf notes), everybody in the sophisticated-and-well-monied segment is increasingly forced to purchase it.
> In this it is like asking a vendor for HIPAA-compliant services. Yes, enjoy 2X on the invoice.
https://twitter.com/patio11/status/1481293496506253321
I quote tweeted it and said:
> An interesting question is if/when will SSO become so prevalent that it won't be a point of pricing leverage any more?
> After all you used to have to pay (a fair bit) for SSL certs, until the industry recognized the benefits of them being widespread.
https://twitter.com/mooreds/status/1481300034448760842
I fully expect at some point in the future SSO will be as prevalent as SSL support is now.
I wish there was a hall of fame of vendors who allow SSO for free or a low price. And I don’t mean “Sign-in with Google” - not everyone has company managed Google accounts. Of the top of my head I can think of Mapbox and AWS where it’s free. Atlassian charges $4/month covering all their products (cheap if you use two or more). Any more good examples?
Earlier quoted context omitted.
sign-in with Microsoft is indeed SSO.
"Sign in with..." is almost SSO. Federated authentication employs centralized authentication and can even support third-party identity providers. However, single sign-on is exactly like it sounds: You sign on once and have access to all SSO-enabled applications. This differs from "sign in with..." offerings, because you often have to sign in again. Compare this to, say, the user hub of Google Workspace: You are prese…