TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Show HN: Osso – Open-source SAML SSO service

41 点作者 sbauch超过 4 年前

9 条评论

grinich超过 4 年前
I hate to have to do this, but given this is a rip-off of a WorkOS product I feel I need to step in here. (I&#x27;m the founder of WorkOS.)<p>Sam and Michael were both brief employees at WorkOS in 2020 where they contributed to our product and were privy to our full codebase, strategy, and roadmap. (We are very transparent internally.)<p>Both of them were let go from the company. Sam then decided to start working on this open source clone of WorkOS. There are striking similarities in the API structure and architecture of Osso, enough to clearly not be coincidence. Our lawyers sent him a cease and desist but he has persisted working on the project.<p>This is an unfortunate situation and it’s disappointing to see Sam misrepresent the origins of the Osso project. (He even took WorkOS off his LinkedIn.)<p>Personally I’m a big fan of open source and open source based business models. (I was responsible for open sourcing Nylas Mail and the underlying Nylas Sync Engine while I was CEO there.) But this form of blatantly ripping someone else’s work and passing it off as your own just isn’t right.<p>We’re prepared to pursue legal action against Osso if needed, but honestly we’ve just been too focused on growing WorkOS. Today WorkOS is already powering enterprise SSO for a bunch of big companies and also many startups&#x2F;SMBs and growing quickly. We’re also SOC 2 Type 2 certified and super well funded (unannounced rounds) with a fantastic team.<p>So I’m posting this mostly to call-out bad behavior and to stand up for our team’s hard work. They deserve it.<p>More background on WorkOS for those curious:<p>- WorkOS “Show HN” launch (March 2020): <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=22607402" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=22607402</a><p>- Our recent Fall Release (Nov 2020): <a href="https:&#x2F;&#x2F;youtu.be&#x2F;JP-9wVoqy4A" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;JP-9wVoqy4A</a><p>- “Crossing the Enterprise Chasm” (August 2019): <a href="https:&#x2F;&#x2F;youtu.be&#x2F;IR2QZQrzoiA" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;IR2QZQrzoiA</a><p>- WorkOS API Docs: <a href="https:&#x2F;&#x2F;workos.com&#x2F;docs" rel="nofollow">https:&#x2F;&#x2F;workos.com&#x2F;docs</a>
评论 #26019391 未加载
评论 #26021553 未加载
评论 #26056265 未加载
apkallum超过 4 年前
Intentionally shifting the meaning of the term opensource is unacceptable. Open source means surrendering your monopoly over commercial exploitation of your code.<p>See Drew DeVault&#x27;s article: <a href="https:&#x2F;&#x2F;drewdevault.com&#x2F;2021&#x2F;01&#x2F;20&#x2F;FOSS-is-to-surrender-your-monopoly.html" rel="nofollow">https:&#x2F;&#x2F;drewdevault.com&#x2F;2021&#x2F;01&#x2F;20&#x2F;FOSS-is-to-surrender-your...</a>
评论 #26018258 未加载
Naac超过 4 年前
&gt;&gt; Osso is an open source microservice...<p>It&#x27;s not. At the bottom of the README you then state:<p>&quot;While not technically an open source license...&quot;<p>It&#x27;s flat out <i>not</i> an open source license. And I think its disingenuous to have &quot;open source&quot; right in the first paragraph of the README.<p>I think you should change any mention of Open Source to &quot;Source Available&quot;, to avoid this confusion.<p>The fact that the acronym OSS is in the company name is probably not helping.<p>EDIT: I went ahead and created a PR :)<p><a href="https:&#x2F;&#x2F;github.com&#x2F;enterprise-oss&#x2F;osso&#x2F;pull&#x2F;706" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;enterprise-oss&#x2F;osso&#x2F;pull&#x2F;706</a>
评论 #26018387 未加载
评论 #26017500 未加载
评论 #26018446 未加载
sbauch超过 4 年前
Hey HN! We&#x27;re Sam, Sam, and Michael, the founders of Osso (<a href="https:&#x2F;&#x2F;ossoapp.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;ossoapp.com&#x2F;</a>)<p>Osso is open-source software for integrating SAML SSO with any web application. It provides an Admin UI to onboard your customers, generates custom documentation to configure your app in a customer&#x27;s Identity Provider (IDP), handles SAML authentication against IDPs and provides your app normalized JSON profiles as part of an OAuth 2.0 code grant authorization flow.<p>We started working on Osso together as a way to keep in touch and distract ourselves from, well, *gestures broadly at everything*. We chose to work on something that each of us came up against during our careers: supporting SAML SSO. Between the three of us, we&#x27;ve built internal tools where SAML was required by IT and struggled to sell SaaS products that didn&#x27;t offer SAML SSO to enterprises who required it. We&#x27;ve also been <i>users</i> of various IDPs, limiting us from accessing the apps we wanted at work when they only included SAML SSO on the way-too-expensive Enterprise plan.<p>Every successful SaaS company builds SAML SSO eventually but it&#x27;s never a top priority and nobody takes time to <i>really</i> understand it. If your customers want SAML, it&#x27;s a great problem to have but chances are there are thousands of other things on your list. Most teams end up kicking it down the road, which can lead to lost sales opportunities. Companies end up piecing something together that kind of works but creates technical debt or support burden, or they spend thousands of dollars on Auth0 or AWS Cognito, but still lack customer docs or a streamlined flow for SAML onboarding.<p>So we&#x27;re trying to simplify things for SaaS companies to make SAML SSO a more accessible option. We took existing open-source software and added the last 10% to make integrating a scalable, sellable, and serviceable SAML SSO solution as easy as possible. All the code is available on Github for you to run on your own, but we also offer a SaaS solution where we&#x27;ll manage an Osso instance for you.<p>Osso:<p>• Treats SAML like OAuth - connect your app to an Osso instance via OAuth, and Osso will handle the SAML authentication and return normalized JSON profiles<p>• Enables first class support for Azure Active Directory, Okta, OneLogin, Ping, Google, and Salesforce, yet works with any IDP that supports SAML 2.0<p>• Features an Admin UI for customer support &#x2F; success teams to onboard and support customers<p>• Provides a convenient interface for technical teams to create and roll OAuth clients and their secrets<p>• Generates custom PDFs for step-by-step onboarding for each of your customers<p>If you&#x27;re interested in learning more, start here:<p>— Our docs [<a href="https:&#x2F;&#x2F;ossoapp.com&#x2F;docs&#x2F;quick-start" rel="nofollow">https:&#x2F;&#x2F;ossoapp.com&#x2F;docs&#x2F;quick-start</a>]<p>— Github repos [<a href="https:&#x2F;&#x2F;github.com&#x2F;enterprise-oss" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;enterprise-oss</a>]<p>— Quick video walk-through of Osso [<a href="https:&#x2F;&#x2F;youtu.be&#x2F;Jps3eeZGOr0" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;Jps3eeZGOr0</a>]<p>— Demo instance [<a href="https:&#x2F;&#x2F;demo.ossoapp.com" rel="nofollow">https:&#x2F;&#x2F;demo.ossoapp.com</a>]<p>The back end is a few modular Ruby&#x2F;Rack apps including a GraphQL API and an OAuth 2.0 server, while the front end is a React app written in Typescript. We use a modular and package driven approach, allowing you to customize your Osso instance with theming or middleware, or pick and choose parts of the stack to use, while getting critical updates through our Ruby gems and npm packages. We offer client libraries for Ruby (omniauth-osso) and NodeJS (passport-osso), and are working on React components you can use to interact with your Osso instance, like a login component and a widget to allow your customers to configure SAML themselves.<p>We really appreciate the HN community and the discussion that takes place here, so we hope you&#x27;ll provide honest feedback on Osso. What&#x27;s missing? What should we do differently? Anything you&#x27;d take away? We look forward to reading and responding to your comments, but if you want to speak with us directly you can also email us at hello@ossoapp.com.<p>Thank you! Sam, Sam, and Michael
评论 #26018127 未加载
评论 #26017462 未加载
jcutrell超过 4 年前
Congrats on the launch folks! Would you mind outlining why SAML specifically is hairy? How is it different from OAuth (for people who aren&#x27;t doing a bunch of auth work on a daily basis, or haven&#x27;t reached a scale where SAML is an issue yet)?
评论 #26003406 未加载
forks超过 4 年前
Congrats on the launch! I work at Oso [1], also an NYC-based security startup but with half as many consonants and co-founding Sams. <i>cue spiderman meme</i><p>[1]: <a href="https:&#x2F;&#x2F;www.osohq.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.osohq.com&#x2F;</a>
评论 #26018812 未加载
dtien超过 4 年前
Wow, this is amazing at first glance. Will definitely have to dive into to see that it hits all the requirements. But as someone who trodded down this rathole when a client asked if we supported SSO, it would be an amazing utility to have around.<p>How battle tested is this with real companies and different IDPs?<p>In any case, congrats on the launch and will definitely be taking a closer look.
评论 #26017616 未加载
rocky_raccoon超过 4 年前
Can Osso act as an IdP or are there any plans to build this in the future?<p>I&#x27;ve been struggling for a long time now trying to find a good IdP I can use to integrate with my existing user database.
评论 #26018204 未加载
jarym超过 4 年前
This is excellent and much needed. SAML is indeed a pain.<p>Now my question is how safe&#x2F;secure is your XML parsing? Because that’s been a source of vulnerabilities in other libraries.
评论 #26017637 未加载