News for hackers. Stuff that matters.
Re:The SSO Wall of Shame by go_prodev on Wednesday April 27, 2022 @05:49AM (#31178090)
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.

Re:The SSO Wall of Shame by jabroni_salad on Wednesday April 27, 2022 @09:24AM (#31179546)
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

Re:The SSO Wall of Shame by mooreds on Wednesday April 27, 2022 @09:39AM (#31179741)
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 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.

Re:The SSO Wall of Shame by jbboehr on Wednesday April 27, 2022 @08:15PM (#31187388)
> 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?

Re:The SSO Wall of Shame by mooreds on Thursday April 28, 2022 @04:34PM (#31197868)
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 by deepakprab on Thursday April 28, 2022 @07:11PM (#31199387)
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 by ryancp on Thursday April 28, 2022 @06:12AM (#31190754)
I am a big fan of Keycloak as it’s been mentioned a few times in previous comments. Maybe this could help someone interested in implementing SSO, but currently working on a full stack starter kit that has Keycloak support/integration included: https://appcket.org.
Re:The SSO Wall of Shame by realityking on Wednesday April 27, 2022 @06:14AM (#31178214)
Are you looking to offer SSO to users of your SAAS app? Firebase does support SAML: https://medium.com/@tfalvo/single-sign-on-sso-for-your-fireb...

Both Microsoft Azure AD and JumpCloud have free plans you can use for testing.

Re:The SSO Wall of Shame by easton on Wednesday April 27, 2022 @11:20AM (#31181020)
And Microsoft offers a Microsoft 365 Developer Program which gives you 25 accounts with the maximum license (so Azure AD Premium/Conditional Access/etc) as long as you promise not to use them for prod (and they wipe the tenant every 90 days).

https://developer.microsoft.com/en-us/microsoft-365/dev-prog...

Re:The SSO Wall of Shame by spacemanmatt on Wednesday April 27, 2022 @07:49AM (#31178746)
You might be a great candidate for Keycloak.
Re:The SSO Wall of Shame by go_prodev on Monday May 02, 2022 @04:37AM (#31232641)
Looks great, thanks for the suggestion
Re:The SSO Wall of Shame by aliswe on Wednesday April 27, 2022 @06:22AM (#31178249)
sign-in with Microsoft is indeed SSO.
Re:The SSO Wall of Shame by nulbyte on Wednesday April 27, 2022 @07:48AM (#31178738)
"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 presented a list of applications, and when you click on one, you are instantly signed into it. This is SSO.