Identity Management Category: Single Sign-On

Identity Management Category Single Sign-On

The identity and access management (IAM) market is one of the most active IT markets today. An important category within the IAM market is single sign-on (SSO). However, like all modern IAM categories, the SSO space is in a state of transition. This blog discusses the future of the identity management category: single sign-on. But first, we should outline the development of IAM in general.

A Brief History of IAM

A brief history of Identity Management Category: Single Sign-On

To understand the current state of the IAM SSO market, we need to go back to the beginning of the modern era of IAM. In other words, we need to go back to the advent of the Lightweight Directory Access Protocol, or LDAP for short.

LDAP was created in 1993 at the University of Michigan as a lightweight alternative to the precursor X.500 directory service protocol. Tim Howes, now a JumpCloud advisor, was the co-inventor.

LDAP was essentially the subset of X.500 protocols related to directory access (e.g., DAP) with a few enhancements. What made it lightweight was the fact that LDAP required less bandwidth and was more easily implemented over networks (Wikipedia).

LDAP went on to become the internet standard for directory services a few years later. LDAP would even become a foundational aspect for two powerful on-prem directory services solutions – OpenLDAP and Microsoft® Active Directory® (AD).

Of course, today we know that OpenLDAP is used more in technical situations with Linux®, for example, whereas Active Directory has become the central directory for Windows® based systems and applications. Nevertheless, both of these solutions worked great for on-prem systems and other resources that were popular around the turn of the century.

However, as web applications appeared on the market in the mid-2000s, these solutions started to break down.

Traditional Single Sign-On Implementation

Challenges with the Identity Management Category: Single Sign-On

The trouble with OpenLDAP and Active Directory was that they didn’t connect with IT solutions in the cloud. This was because web applications leveraged different authentication protocols, like SAML, for example. The result was the creation of a new generation of web application (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 166 posts and counting.See all posts by vince-lujan