Introduction to Identity-as-a-Service (IDaaS)

Introduction to IDaaS

The term Identity-as-a-Service (IDaaS) joined our lexicon in the late 2000s as a description for web application single sign-on (SSO) platforms. Since then, though, the term has taken on a new and broader meaning. In this article, we’ll provide a modern introduction to Identity-as-a-Service.

Establishing IDaaS

When web application SSO solutions first emerged, they wanted to brand themselves as a more significant solution than just connecting users to web apps. These vendors were interested in differentiating themselves from their on-prem identity provider brethren. Although they were mostly used in tandem with directory services like Microsoft® Active Directory® (AD), web app SSO solutions were cloud-based. So, to accentuate their cloud heritage and Software-as-a-Service (SaaS) delivery, SSO developers coined the term, Identity-as-a-Service.

Of course, to get a category name to stick, you need to convince the analysts and pundits that it is a new and interesting one. These constituents were also excited to create a new category because of building interest in cloud-based IT management tools at the time. While the name wasn’t very accurate (it was cloud-based web application SSO, after all), it stuck and a fancy new category in the identity and access management space was born.

Early IDaaS


The first generation of IDaaS was just what we said, web application SSO. IT organizations would have their on-prem directory service, in most cases Active Directory, and federate those credentials to the web application SSO platform. While the identity was really stored within the on-prem directory service and the IDaaS platform was essentially just extending it to web applications, the concept was still quite useful.

Over time, these first generation Identity-as-a-Service platforms became quite popular. The IT landscape underneath them, however, was shifting and morphing with new resources. macOS® and Linux® systems, AWS® cloud infrastructure, NAS appliances and Samba file servers, and more entered the space. These new options gave first generation IDaaS solutions a run for their money, as these SSO solutions couldn’t help federate AD to the new types of IT resources. The result was not necessarily that first generation IDaaS solutions weren’t (Read more...)

*** This is a Security Bloggers Network syndicated blog from Blog – JumpCloud authored by Zach DeMeyer. Read the original post at:

Zach DeMeyer

Zach DeMeyer

Zach is a writer and researcher for JumpCloud with a degree in Mechanical Engineering from the Colorado School of Mines. He loves being on the cutting edge of new technology, and when he's not working, he enjoys all things outdoors, making music, and soccer.

zach-demeyer has 223 posts and counting.See all posts by zach-demeyer