By Jon Griffin Posted June 2, 2017
If you’ve been following along with this blog series, you likely already know the resume of Tim Howes. For those who have stumbled across this blog on its own though, we’ll give a brief rundown. Currently, Tim Howes is the CTO at ClearStory Data and serves as the executive chairman of Know Yourself. The former of the two is a leading provider of fast-cycle data intelligence, and the latter is a organization that aids children in the process of acquiring self literacy. He also sits on JumpCloud’s Technical Advisory Board.
On top of this, Howes played a major role in the development of modern IT. From inventing the LDAP protocol in 1993 to shaping the SaaS and IaaS model we see today it is clear to see how impactful his role in the world of tech has been. Due to this experience, we recently sat down with Tim to discuss the origins of LDAP and what he thinks the future of IT will look like. This is part three of a four-part series on Howes’ answers to our questions. Tim Howes Interview, Part 3: Microsoft, LDAP, and the Directory
Q: To what extent is Microsoft solving the problem with Azure® and Active Directory®?
Tim Howes: Microsoft’s biggest strength is their huge installed base – but it’s also their biggest weakness.
They’ve got millions of customers using Active Directory and the whole suite of Microsoft products – and so instead of designing with a fresh perspective, taking in the hundreds of services that are outside of Microsoft’s control and the cloud, they’re designing while looking inward, at their existing products. In other words, they’re looking backward.
That’s what’s happening with Azure Active Directory. They recognize that organizations are moving to the cloud and so they’ve developed Azure to facilitate that transition. But because they have a vested interest in maintaining Active Directory’s place in the market, they’re keeping one foot still on-prem.
It’s not necessarily a terrible thing, it’s just that their design decisions are biased toward their own self interest, as opposed to using whatever would make the most sense.
It reminds me of when Microsoft got forced into using LDAP. There was this Internet community that was focused on establishing open standards. They put pressure on Microsoft to adopt LDAP and eventually they built LDAP into Active Directory to accommodate the demand. But if you look carefully at the way they integrated LDAP with Active Directory, it wasn’t standard, it was in their own very Microsoft way.
Continue Reading the Interview Series with Tim Howes
Part 1: Origins of LDAP and DaaS
Part 2: Securing Decentralized IT
Part 3: Microsoft, LDAP, and the Directory
Learn More about Cloud LDAP
We’re proud to say that at JumpCloud, we’re helping pave the way for Cloud LDAP with our LDAP-as-a-Service offering, which simplifies LDAP management and configuration dramatically. Stop wasting time installing and setting up the networking pieces for LDAP. With JumpCloud’s LDAP-as-a-Service, the full overhead of managing and ensuring availability an LDAP instance is taken care of for you.
If you want to see what this looks like for yourself, you’ll be happy to find out that you can get started for free with 10 systems when you sign up for JumpCloud here.
Find Tim Howes Online
Tim has contributed to this blog in the past with his post on his vision for the future of directory services. You can follow Tim Howes on Twitter here, or check out the official pages for ClearStory Data and Know Yourself.