5 ms·
That's exactly why we built WorkOS. It's like "Stripe for SSO/SAML." Shameless plug for my startup. Hope that's still ok on HN :) https://workos.com/ https://
by grinich 6y ago
That's exactly why we built WorkOS. It's like "Stripe for SSO/SAML."
Shameless plug for my startup. Hope that's still ok on HN :)
https://workos.com/ https://workos.com/
- ec109685 6y agoThis sits between a company’s ActiveDirectory and something like Okta? Or is it more like Sail Point that lets you write logic to link everything up?
- grinich 6y agoIt’s infrastructure for SaaS apps to easily connect to all the different systems used in the enterprise, including Okta, OneLogin, ActiveDirectory, Workday, etc.
- catmanjan 6y agoProbably a dumb question, everything in my sphere is active directory - why would you have more than one identity provider?
- grinich 6y agoIf you’re a developer building an app, your customers use a variety of different systems. These are fragmented and you need to support all of them, not just Active Directory.
- catmanjan 6y agoThe previous post said "the enterprise" which makes me think of a singular organisation using all of them - maybe I'm misunderstanding, but why would a single org use more than one?
- grinich 6y ago"The enterprise" is jargon for "the enterprise market." It's rare that a company will use multiple identity systems, but there exists lots of fragmentation across the large companies, which makes building a universal solution into your app very time consuming.
- closeparen 6y agoWorkday: HR system of record, source of truth on which accounts should be provisioned and deprovisioned in AD. Active Directory: holds those accounts. Okta/OneLogin: facilitates use of AD accounts to log in to webapps.
- catmanjan 6y agoAh thanks, I thought he meant they were all being used as identity providers - this makes more sense