3 ms·
As others have pointed out, this article is both a) a valid problem, especially for small products breaking into enterprise and b) and advertisement for a produ
by madmax108 4y ago
As others have pointed out, this article is both a) a valid problem, especially for small products breaking into enterprise and b) and advertisement for a product (WorkOS)
What I would be interested to know is: What open source alternatives exist which tackle this problem and how battle-tested are they (esp. given than SSO differs between org to org)? With a product I built, I just paid the Okta tax and had Okta handle all the complexity of integrating with external systems while providing a single interface for me to interact with (which on the surface is the same thing WorkOS promises), but if I'm inclined to build this out myself, what are the alternatives?
I see a lot of devs, especially on HN, complain about http://sso.tax http://sso.tax, but until you build a product for exterprise, you'll really not understand the time and effort this takes (and all of this takes away time and effort that could be spent building your product)
- caloique 4y agoCurious to hear more about other alternatives to building it internally, lately I've heard a few people claiming that they built it in 1 - 2 days. Still don't know how. There are good open source solutions that let you plug and play these enterprise features (I am biased here). But instead of thinking about the problems with implementing Single Sign-On, I think we should focus on a bigger problem: How can we make security accessible and simple for developers? I am not saying don't charge for SSO, I know it helps startups be sustainable, but here is where I truly believe that open source is one of the key answers.
- caloique 4y agohttps://github.com/boxyhq https://github.com/boxyhq :)