3 ms·

If anyone's looking for an Auth0 alternative, come check out WorkOS! It's like Stripe for enterprise features, including SSO/SAML, Directory/SCIM, and more. h

If anyone's looking for an Auth0 alternative, come check out WorkOS! It's like Stripe for enterprise features, including SSO/SAML, Directory/SCIM, and more. https://workos.com/docs https://workos.com/docs (I'm the founder.) Edit: Here’s our launch last year: https://news.ycombinator.com/item?id=22607402 https://news.ycombinator.com/item?id=22607402

btown 6y ago
This really looks amazing! I saw your post describing your product in relation to Auth0/Okta at https://news.ycombinator.com/item?id=26070302 https://news.ycombinator.com/item?id=26070302 and it makes a ton of sense. Many (most?) enterprise-facing startups don't start out that way, and it's painful in practice (and in principle!) to be power-sold to "lift" your existing users into a solution like Auth0, just to accept SAML logins for new users. And pricing per connection is infinitely more justifiable than pricing per user, especially in that context, especially with today's acquisition removing any downwards price pressure on that per-user pricing!!! I might reach out to you with some questions about our use cases - we're in early conversations with an enterprise client who uses Auth0 for their user management, and ideally we'd be able to use their Auth0 as an IDP for SSO into our existing Django application. Would also love to pick your brain on potential solutions for B2B2C use cases - your Admin Portal concept reminds me very much of a page I've written far too often in the past :) Feel free to reach me as well at btown.hn@gmail.com.
- grinich 6y ago
  Yep, we can definitely support Auth0 as an IdP. It's a less common set up (versus IdPs like Okta or Azure AD) but still something we support. Feel free to send me a note. (Or anyone reading this too!) I'm mg@workos.com
duncans 6y ago
Had a quick look at your docs for integrating with Azure AD SAML https://workos.com/docs/integrations/azure-ad-saml https://workos.com/docs/integrations/azure-ad-saml and wondered why you don't make use of SAML metadata URLs that contain all this configuration? For example the signing certificates, ACS, Reply/ACS URL, EntityIDs are all in the metadata xml docs, so you could boil it down to: * Here's the SP metadata URL - upload it into Azure dashboard here ... * Grab the "App Federation metadata URL" from the Azure dashboard and paste it into WorkOS here ... (where your app can parse the XML and grab certs, URLs etc) And you're done.
- grinich 6y ago
  We're planning to push all configuration to metadata endpoints for providers who support it. There are additional benefits for refreshing SAML certificates (usually every 5 years) and dynamically adapting to other attributes changing. This will get added to our Admin Portal, which is a pre-built experience for IT admins to configure SSO connections: https://workos.com/docs/admin-portal/guide/introduction https://workos.com/docs/admin-portal/guide/introduction Unfortunately the metadata URL configuration path isn't universally supported. I'm hoping FastFed solves this, but all that is still in working group / pre-RFC. https://openid.net/wg/fastfed/ https://openid.net/wg/fastfed/
ryanjodonnell 6y ago
We use WorkOS at Cleary for SSO with microsoft exchange - works great and the team is super responsive and friendly. Thanks @grinich!
jcmfernandes 6y ago
We are happy WorkOS customers at hopin.com :) their SDKs make integration dead easy and their team is super responsive. Thanks @grinich and all the WorkOS team!

btown 6y ago

This really looks amazing! I saw your post describing your product in relation to Auth0/Okta at https://news.ycombinator.com/item?id=26070302 https://news.ycombinator.com/item?id=26070302 and it makes a ton of sense. Many (most?) enterprise-facing startups don't start out that way, and it's painful in practice (and in principle!) to be power-sold to "lift" your existing users into a solution like Auth0, just to accept SAML logins for new users. And pricing per connection is infinitely more justifiable than pricing per user, especially in that context, especially with today's acquisition removing any downwards price pressure on that per-user pricing!!! I might reach out to you with some questions about our use cases - we're in early conversations with an enterprise client who uses Auth0 for their user management, and ideally we'd be able to use their Auth0 as an IDP for SSO into our existing Django application. Would also love to pick your brain on potential solutions for B2B2C use cases - your Admin Portal concept reminds me very much of a page I've written far too often in the past :) Feel free to reach me as well at btown.hn@gmail.com.

grinich 6y ago
Yep, we can definitely support Auth0 as an IdP. It's a less common set up (versus IdPs like Okta or Azure AD) but still something we support. Feel free to send me a note. (Or anyone reading this too!) I'm mg@workos.com

duncans 6y ago

Had a quick look at your docs for integrating with Azure AD SAML https://workos.com/docs/integrations/azure-ad-saml https://workos.com/docs/integrations/azure-ad-saml and wondered why you don't make use of SAML metadata URLs that contain all this configuration? For example the signing certificates, ACS, Reply/ACS URL, EntityIDs are all in the metadata xml docs, so you could boil it down to: * Here's the SP metadata URL - upload it into Azure dashboard here ... * Grab the "App Federation metadata URL" from the Azure dashboard and paste it into WorkOS here ... (where your app can parse the XML and grab certs, URLs etc) And you're done.

grinich 6y ago
We're planning to push all configuration to metadata endpoints for providers who support it. There are additional benefits for refreshing SAML certificates (usually every 5 years) and dynamically adapting to other attributes changing. This will get added to our Admin Portal, which is a pre-built experience for IT admins to configure SSO connections: https://workos.com/docs/admin-portal/guide/introduction https://workos.com/docs/admin-portal/guide/introduction Unfortunately the metadata URL configuration path isn't universally supported. I'm hoping FastFed solves this, but all that is still in working group / pre-RFC. https://openid.net/wg/fastfed/ https://openid.net/wg/fastfed/

ryanjodonnell 6y ago

We use WorkOS at Cleary for SSO with microsoft exchange - works great and the team is super responsive and friendly. Thanks @grinich!

jcmfernandes 6y ago

We are happy WorkOS customers at hopin.com :) their SDKs make integration dead easy and their team is super responsive. Thanks @grinich and all the WorkOS team!