Managed True Single Sign-On™

Managed True Single Sign-On™

The concept of “True Single Sign-On™” can be traced back to the early days of Microsoft® Active Directory® and the domain controller. Of course, it wasn’t called True SSO back then, but the concept (one identity to provision/deprovision access to all resources) has always been in the back of IT admins’ minds. With the rise of the cloud, True SSO started to become more difficult to achieve. Multiple solutions would be needed, with siloed identities occasionally popping up for various unsupported services. Now, a managed True Single Sign-On solution has emerged that is changing that, offering a centralized way to connect users to virtually any IT resource regardless of platform, protocol, provider, or location.

Why True SSO Was Fading Over the Years

Could Managed True Single Sign-On solve the problem

If we go back to the early 2000s when Active Directory was making its push into enterprise environments, it’s easy to see how their concept of True SSO was designed to work. Essentially, admins only needed to use the domain controller to grant their users access to all of the IT resources needed. This meant Windows systems and servers, file servers, and even the network itself were all able to be touched by the domain controller. The concept was designed so that all a user would need to do was login to their Windows machine when accessing the network, and then simply access whatever they needed without having to login again.

This approach to user management and access worked well for both admins and end users, but was predicated on two key factors. The domain controller approach only worked as intended while the network was all Windows and located on-prem. While this may have been the case in the early 2000s when AD was introduced, it surely is not the case today. The introduction of web applications and cloud infrastructure dramatically shifted IT resources and how they were accessed by end users. On top of that, the rise of Mac and Linux machines in the enterprise made it even more difficult for the SSO process to work due to them being non-Windows systems. There were many 3rd party (Read more...)

*** This is a Security Bloggers Network syndicated blog from JumpCloud authored by Jon Griffin. Read the original post at:

Jon Griffin

Jon Griffin works as a writer for JumpCloud, an organization focused on bringing centralized IT to the modern organization. He graduated with a degree in Professional and Technical Writing from the University of Colorado Colorado Springs, and is an avid learner of new technology from cloud-based innovations to VR and more.

jon-griffin has 88 posts and counting.See all posts by jon-griffin