As cloud adoption in IT continues to accelerate, vendors are introducing cloud directory offerings to the space. Some of these, however, aren\u2019t exactly what you\u2019d expect. This head scratching has led IT admins to wonder what a cloud directory is and how it is different from the on-prem identity provider (IdP) or traditional directory service they are accustomed to. <\/p>\n\n\n\n
In truth, a cloud directory isn\u2019t just a cloud-washed version of the on-prem directory service or a simple relational hierarchy of cloud identities; rather, it\u2019s a new generation identity and access management (IAM) platform.<\/p>\n\n\n\n
Historically, the directory, or identity provider, lived on-prem and was most often delivered in the form of Microsoft Active Directory, where OpenLDAP was used as the open source alternative. With the IT network largely Windows-based and on-prem, it made a great deal of sense that a Microsoft solution helped manage user access. <\/p>\n\n\n\n
In short, the on-prem identity provider would connect users to their IT resources including systems, applications, files, and even the network itself. When everything was Windows, it was easy to see why Active Directory and the domain controller<\/a> were so valuable. End users would simply login to their Windows laptop or desktop, and they had access to whatever they were entitled to within the on-prem network.<\/p>\n\n\n\n
That identity and access management model started to break down as the IT network shifted away from being on-prem and Windows-based. AWS cloud servers started becoming popular, Mac and Linux machines infiltrated the network, and Exchange was replaced for Google Workspace and Microsoft 365. Active Directory, the on-prem directory service, started to struggle.<\/p>\n\n\n\n
While it would be a straightforward conclusion to move the directory service up to the cloud with everything else, that was not the case for Active Directory and other directories. The identity provider remained cemented on-prem and unable to adapt to the changing IT landscape. <\/p>\n\n\n\n
Seeing this vacuum, vendors began releasing add-ons to the traditional identity provider that would help to span the gap between the ever-expanding cloud and on-prem, Windows environments. These include identity bridges, web-application single sign-on (SSO) tools, privileged access management, multi-factor authentication, governance solutions, and more. While they helped to add the functionalities missing from AD and other directories, these add-ons couldn\u2019t capture the full IAM picture.<\/p>\n\n\n\n
As all of these changes occurred, a next generation identity management platform emerged to enable IT organizations to shift to the cloud and non-Windows resources effectively and create a Domainless Enterprise<\/a>. <\/p>\n\n\n\n
Called the cloud directory, this cloud identity provider securely managed and connected users to their systems (Windows, Mac, Linux), web and on-prem applications via LDAP and SAML, cloud and on-prem servers (e.g. AWS, GCE, Azure), physical and virtual file servers (Samba, NAS appliances, Box, G Drive, etc.), and wired and WiFi networks through RADIUS. This cloud directory is JumpCloud Directory Platform<\/a>.<\/p>\n\n\n\n\n