Single Sign-On Alternative

single sign-on alternative

Single Sign-On (SSO) is a hot category in the cloud identity and access management (CIAM) space. This is because many IT organizations are still locked into the on-prem Microsoft® Active Directory® (AD) ecosystem. SSO has historically enabled IT admins to extend AD identities to web applications and cloud resources. Yet, as more organizations seek to eliminate their on-prem IT infrastructure, admins have no choice but to look for alternatives to AD. Since conventional SSO was designed to modify on-prem environments, many forward-thinking orgs find themselves looking for a single sign-on alternative as well.

The good news is that a next generation single sign-on alternative has emerged that is changing the way IT admins think about SSO. In short, it’s called JumpCloud® Directory-as-a-Service®, and it offers SSO access to virtually any IT resource, including systems, apps, file servers, and networks. We like to call this concept True Single Sign-On. However, we should discuss traditional SSO before we dive into the benefits of True SSO with JumpCloud.

A Brief History of Single Sign-On

identity management active directory

While the use of the term Single Sign-On didn’t take hold until the mid-2000s, the concept of SSO first appeared in 1999 with the release of Active Directory. Most IT networks were Windows-based and on-prem, at the time. Naturally, AD flourished in this type of environment. One of the key benefits was that users could access all of their IT resources by simply logging into their system, and the Kerberos protocol would help them get what they needed. In other words, it was a “single sign-on” experience. It was a huge hit.

However, the nature of IT started to change in the mid-2000s as web applications like Salesforce came to market. This category of solution, among others, could not be bound to an AD domain and didn’t leverage Kerberos. Consequently, AD identities could not be leveraged to authenticate user access. The end result was that IT admins were forced to manage user access to cloud applications independently.

Active Directory fails in the cloud

It was this limitation with AD that inspired the creation of an entire category of first (Read more...)

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

Vince Lujan

Vince is a documentation and blog writer at JumpCloud, the world’s first cloud-based directory service. Vince recently graduated with a degree in professional and technical writing from the University of New Mexico, and enjoys researching new innovations in cloud architecture and infrastructure.

vince-lujan has 169 posts and counting.See all posts by vince-lujan