Nimble Directory Service

What is a nimble directory service?

IT admins need to constantly be on their toes, given the spread of IT resources leverageable by today’s workforce. Like a boxer, admins must roll with the “punches” that the modern workplace can throw at their directory services’ identity management capabilities. Some directory services, however, can be flat-footed and aren’t designed to adapt to changes in the IT scene. You can’t authenticate like a butterfly or authorize like a bee without a nimble directory service.

The Reigning, Aging Champ

When it comes to directory services, none is more widely used than the legacy Microsoft® Active Directory® (AD or MAD). From its inception nearly twenty years ago, MAD has been an on-prem mainstay for IT admins due to its sleek Windows integration and group policy objects (GPOs) among other features. While it may have been the benchmark standard of its day, MAD is anything but nimble. It’s hard to be swift when you’re tied on-prem by miles of Ethernet cable and weighed down by big, blocky servers. It’s even harder to be nimble when you have trouble federating user access to non-Windows systems, like Mac® or Linux® devices.

See, today’s IT scene is constantly changing, and a directory service needs to be able to react to these changes just as quickly. Since Active Directory hit the scene, the IT market has evolved dramatically. Software-as-a-Service (SaaS) applications, starting with Salesforce and others, have changed the way the workforce accesses resources. The cloud has offloaded the weight of on-prem file storage, computing servers, and more off of IT shops. Workers have become remote, leveraging WiFi to make work happen virtually anywhere.

Replace AD with JumpCloud

A Flat-footed Directory

MAD, however, has practically sat like a stone amidst the innovations of the cloud era. When dealing with web applications, the on-prem AD needs single sign-on (SSO) tools to bridge the gap between its servers and cloud-based work resources. IT admins need to implement identity bridges to link their MAD instance to their users’ Mac and Linux systems. VPNs (virtual private networks) are required to permit remote users to access network resources. With all of (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 168 posts and counting.See all posts by zach-demeyer