{"id":28859,"date":"2019-02-19T09:00:48","date_gmt":"2019-02-19T16:00:48","guid":{"rendered":"https:\/\/jumpcloud.com\/?p=28859"},"modified":"2024-11-14T18:14:47","modified_gmt":"2024-11-14T23:14:47","slug":"why-use-directory-services","status":"publish","type":"post","link":"https:\/\/jumpcloud.com\/blog\/why-use-directory-services","title":{"rendered":"Why Use Directory Services?"},"content":{"rendered":"\n
As organizations think about the IT infrastructure solutions they need, some have come to wonder, \u201cWhy use directory services?\u201d Directory services have been a core part of IT networks for a few decades now, but (until recently) they haven\u2019t adapted to the cloud-forward, heterogeneous IT landscape most IT organizations are equipped with. So, it makes sense to question whether or not they should still be used. To provide a complete answer, it\u2019s important that we take a step back and understand <\/span>what is a directory service<\/span><\/a>, and the history behind this core IT management tool. <\/span><\/p>\n\n\n\n A directory service is a piece of technology used to store information about employees like usernames, passwords, contact information, and a lot more. Not only does a directory service store this user information, but it also maps out the relationship users have with the digital assets used in the company. For instance, a directory service will map that employees in the finance department have access to accounting applications, but they don\u2019t have access to code repositories. So if an employee from the finance department tried to gain access to a code repository, they wouldn\u2019t be able to because they don\u2019t have the right to access that resource. Having these kinds of <\/span>access controls<\/span><\/a> in place helps maintain a strong security foundation. <\/span><\/p>\n\n\n\n Ideally, a directory service is able to integrate with all of the IT resources used in an organization, so that IT admins can centrally manage what users have access to and what they don\u2019t need access to. This setup is preferred because IT admins gain more control, security, and efficiency in managing their environment while employees benefit from having an easier time accessing everything they need to get their work done. In the past, a centralized environment was easily attainable thanks to the IT landscape at the time (mainly Windows-based) and the long-time leading on-prem identity provider\u2014<\/span>Microsoft<\/span>\u00ae<\/span> Active Directory<\/span>\u00ae<\/span><\/a> (MAD). <\/span><\/p>\n\n\n\n Microsoft Active Directory was released in 1999 to solve the <\/span>user and system management<\/span><\/a> needs of the 1990\u2019s and early 2000\u2019s. You see, most workplaces were already filled to the brim with other Microsoft products. Microsoft didn\u2019t expect for this to change, so MAD was built with the purpose to solely manage users and systems in an on-prem, Windows<\/span>\u00ae<\/span>-centric IT ecosystem. Microsoft also decided to bundle Active Directory with the purchase of <\/span>Windows Server<\/span><\/a> licenses (called CALs), so organizations felt like they were getting it for free. Plus, not only was it \u201cfree\u201d but it worked really well. Organizations were able to provision and control user access to all of their Windows-based IT resources such as the network, servers, applications, and, of course, a user\u2019s laptop or desktop computer. With this one central location for all IT resources, an organization could enroll users for access and disable them across the entire network with ease and efficiency.<\/span><\/p>\n\n\n\n Microsoft\u2019s directory service worked well until the IT landscape started to change. As organizations started to leverage web applications, cloud infrastructure, Mac\u00ae and Linux\u00ae machines, and WiFi networks, user access control started to break down. AD couldn\u2019t easily manage and control access to these non-Windows resources. That spawned the requirement for organizations to purchase a number of add-on solutions to AD such as identity bridges, <\/span>web application single sign-on<\/span><\/a>, MFA, and more. However, this new setup left a lot to be desired from what many were used to with directory services. Not only did IT admins find themselves having to manage users in a variety of solutions, but it was also more expensive, didn\u2019t do a whole lot for security, and created havoc for end users. It was borderline madness, so it makes sense that IT admins are questioning whether to even use directory services nowadays. <\/span><\/p>\n\n\n\n The truth is if your IT environment leverages a lot of cloud solutions and isn\u2019t solely Microsoft-based, a traditional directory service like MAD simply won\u2019t cut it. The good news is that there is a <\/span>next generation directory service<\/span><\/a> that can. It\u2019s called JumpCloud<\/span>\u00ae<\/span> Directory-as-a-Service<\/span>\u00ae<\/span>. <\/span><\/p>\n\n\n\nWhat is a Directory Service?<\/span><\/h2>\n\n\n\n
Meet MAD<\/span><\/h2>\n\n\n\n
Then It Slowly Turned into MAD(ness)<\/span><\/h2>\n\n\n\n
Why Use Directory Services with JumpCloud<\/span><\/h2>\n\n\n