Recently, I came across Canming Jiang's post Democratize SSO for everyone, where the author presents a narrative that 80% of SaaS products are not in SSO Portals, and that implementing SSO can take 3-6 months on average. I disagree with this narrative, but I concede that my opinion is a result of a decade's worth of experience on both sides of single sign-on.
Because I believe that SSO is already easily accessible, I decided to start a new blog series called A Practical Guide to Single Sign-On. The goal of these posts will be to help accelerate developers with implementing SSO in their own products. Some of the topics that I have planned for this series include:
- What is SSO?
- Developer Resources
- No-Code solutions for SSO
- Adding SSO to a single-tenant application using node.js
- Adding SSO to a multi-tenant application using node.js
- What SSO Looks like when it's Feature-Complete
- Tips and Tricks for Troubleshooting SSO
Do you have any additional topics around single-sign on that are troubling you? Drop them below in the comments, I'll try to address them as I author the individual posts.
Single Sign-On SSO is a game changer for simplifying access to multiple services with just one login. If implemented in government portals, like Rajasthan’s, it could streamline access to various citizen services.
Rajasthan SSO