3 ms·
Yep we're already looking at doing this with docs. :) One thing to help with the SAML support is WorkOS.js. It's essentially an embeddable configuration flow,
by grinich 7y ago
Yep we're already looking at doing this with docs. :)
One thing to help with the SAML support is WorkOS.js. It's essentially an embeddable configuration flow, so you don't need to build the UI to collect x.509 certs, generate the ACS URL, etc. Similar architecture to "Plaid Link" so users never leave your app.
Docs here: https://docs.workos.com/sso/embed-workosjs https://docs.workos.com/sso/embed-workosjs
- ucarion 7y agoYeah this is really cool! To your point about WorkOS.js -- how would a customer know where to find their SAML metadata? Some of this can be done inline in WorkOS.js, of course. But no amount of inline docs in WorkOS.js's UI is going to get around the high-level guidance docs, both for your customers ("where do I even start") and your customers' customers ("how do I fit my IdP peg into your SP round hole").
- grinich 7y agoAh yeah I'm talking about two different things. The docs for getting SAML config would be on a separate public site. WorkOS.js is for the IT admin to configure their SSO/SAML integration. With both of these things, you can make SAML fully self-serve and include it in your base tier, which drives adoption and retention in bigger companies.