We are having a lot more nervous takes around legacy LDAP/AD auth mechanisms these days.
It’s an API for easily adding SAML, SCIM, and more. Currently being used in production by Vercel, Planetscale, Webflow, and +200 other apps.
E.g I know nothing about Azure AD but I just emailed the WorkOS setup link to our customer’s IT team, they followed the instructions and it just worked. No back and forth.
Can’t recommend enough.
You probably have to prove that you have these on your roadmap and that you have engineering team that can implement these in not so distant future. That you know these things exist and have will to invest in it in future.
The alternative is that your product becomes a security exception, which infosec teams are more and more unwilling to grant, for pretty good reasons.
The good news for product teams is that there are more and more off-the-shelf options that can be quickly integrated vs. having to start from scratch.
But the main point of this comment is: I think you’re right that “near term roadmap” was good enough a few years ago, but less so now, and continuing to trend towards “not acceptable” if selling to enterprise customers.
(Observations as a recent/former auth PM at a SaaS/PaaS that sold primarily to enterprise customers).