By Zach DeMeyer Posted September 28, 2018
While directory services are at the core of identity and access management (IAM), functioning as a full-fledged directory is not a capability of every IAM platform. At first glance, this statement may sound like a ridiculous one. If a directory service is at the core of IAM, why wouldn’t every platform in the space feature a directory? In today’s definition of IAM, the identity management capability of directory services can often be overlooked in the face of other solutions.
IAM, What IAM?
You could say that the concept of identity and access management dates all the way back to the first instance of computer passwords in the 1960s, but truly transformed into its own space in the 90s with the invention of LDAP and the subsequent arrival of Microsoft® Active Directory® (MAD). The inception of MAD, and the following rise of the directory service, is when enterprises really began to have robust IAM at scale. At the time, given that Windows® systems and resources were the norm, MAD could effortlessly connect users to their systems, resources, and more.
In the years since, the IAM needs of organizations only became more expansive and heterogeneous. This occurrence was mostly due to the rise of the cloud, as well as the uptick in the popularity of non-Windows systems. A variety of IAM micro-tools cropped up in response to the needs of IT admins, specializing in access to web apps or Mac® and Linux® devices. Using these micro-tools meant that admins could, more or less, patch their MAD instance to meet the demands of modern IT.
Today’s Definition of IAM
Some of these added-on solutions have gained a lot of traction in the IAM space, namely single sign-on (SSO) solutions. SSO makes an easier user experience by bridging the distance between cloud applications on the web and on-prem MAD. This functionality has given SSO solutions clout in the industry and, in turn, have even made them more popular than using a directory service in some cases.
Others view IAM as a way to corner their hold on the market. For instance, companies like Amazon and Google have their own versions of IAM directory solutions. These, however, are like MAD in that they are designed to be used first and foremost with their corresponding web solutions, Amazon’s AWS® or Google’s G Suite™ for example. While they may be pitched as a directory service, these solutions tend to be more like a user management/SSO platform than a full directory.
The best approach to identity management isn’t the cobbling together of a variety of incomplete, specialized “add-ons.” Instead, savvy IT organizations are looking for identity management with a broad capabilities, ranging from SSO to network access using RADIUS, system management, and even directory services. This unified approach to identity management is available through JumpCloud® Directory-as-a-Service®.
IAM with JumpCloud®
JumpCloud Directory-as-a-Service (DaaS) is a directory service for the modern era, establishing a new normal for IAM capabilities. With DaaS, admins can manage users’ identities, systems, application and network access, and more, all from one pane of glass. JumpCloud is a third-party solution, so it federates user access regardless of location, platform, protocol, or provider.
To learn more about expanding your identity management capabilities for directory services with JumpCloud Directory-as-a-Service, feel free to contact us or check out our YouTube channel. Looking to check out the DaaS product firsthand? Consider scheduling a demo with one of our product experts or sign up for JumpCloud today. The process is completely free, and so are your first ten users to get you started.