andy89
Joined 3 years ago
Karma
17
Submissions
109
Member since
Apr 11
Recent submissions
Comment · 11 months ago
Comment · 1 year ago
We recently had to implement SSO for a multi-tenant SaaS platform. The usual names came up (Okta, Auth0, Ping, WorkOS, etc.), but the deeper we looked, the more complicated the tradeoffs became.
We created a comparison table across 15 SSO providers — focusing on protocols (SAML, OIDC, SCIM), admin UX, dev experience, pricing models (per user vs. per connection), and use-case fit (CIAM vs workforce IAM).
It’s here if useful: https://ssojet.com/blog/top-10-sso-providers-2024/
Curious how others here navigated this — especially around: - When SCIM or JIT provisioning became non-negotiable - How you handled multi-tenancy or tenant branding - If pricing or vendor lock-in became an issue
Happy to share our notes or answer questions.
Comment · 1 year ago
Thank You
Comment · 1 year ago
Working on a central CIAM knowledge hub — SSO, SCIM, API security, zero-trust, etc.
Noticed most guides out there are too fluffy or scattered. Here's what we’ve got so far: https://ssojet.com/ciam-101
What’s missing? Would love ideas from folks building auth systems.
Comment · 1 year ago
I recently had to wire up SAML-based SSO with Okta for a Next.js project. Most of the resources I found were either outdated or assumed a ton of boilerplate. I ended up combining passport-saml, iron-session, and custom API routes to make it work cleanly with Next.js.
Covered in the guide:
Okta SAML setup + metadata extraction
Configuring Passport strategy
Secure session handling with iron-session
API route-based login/callback/logout flows
Protecting SSR pages and basic user provisioning
Tips for testing locally with ngrok
If you’re building enterprise-ready apps with Next.js and need SAML support, this might save you some time: https://ssojet.com/blog/integrating-okta-saml-sso-with-your-...
Feedback welcome, and I’m happy to help troubleshoot if anyone hits weird edge cases like ACS URL mismatch or certificate issues.
Comment · 1 year ago
Yeah, totally fair — we’ve run into the same thing. Some vendors list SSO/SAML just to check the "enterprise-ready" box, but it's not actually live or usable.
Right now the directory just flags that SSO is publicly claimed, but we’re working on a second pass to add verified protocol support, links to setup docs, and even plan requirements (like Enterprise-only).
If you’ve got examples of false claims, I’d love to include them as edge cases — could help others avoid the same surprises.
You can check out our directory from here: https://ssojet.com/b2b-sso-directory/
Comment · 1 year ago
Here’s the directory: https://ssojet.com/b2b-sso-directory/
No signup, just a public list — feel free to send additions if you think something’s missing.
Comment · 1 year ago
Absolutely — SAML almost always comes up the moment you’re in talks with IT or security teams. It’s a clear signal you're moving upmarket.
https://mojoauth.com/blog/how-to-migrate-to-passwordless-fro...