Directory Services as the Foundation of Organizational Infrastructures

December 31st, 2006 by Tom Adelstein

Your rating: None

If you have followed any of my last six installments about LDAP, then you know we've taken a technical approach to the subject. I wrote the majority of the material in this series as part of an O'Reilly book entitled "Linux System Administration" or simply LSA. You can find a write-up on the book at this link.

The material on LDAP did not make it into LSA for a number of reasons. First, O'Reilly already has an excellent book on LDAP written by Gerald Carter. A 600 page book on Linux system administration doesn't need a repeat of existing work. Secondly, I found open source LDAP a strange animal with which to deal.

And that animal conjures up some interesting observations.

Linux and the open source community has many great projects. However, those projects have limitations in the context of a boundary based enterprise infrastructure. While Linux, as an example, does a beautiful job as an application platform, it lacks some essential elements for creating an enterprise environment capable of serving the needs of organizations. I blame that on a lack of vision and resources by and in the community. I see that as a niche in the competitive landscape.

Perhaps we know what to do to create a secure, manageable environment using Linux but others with extensive resources need to take on that monumental set of tasks required to turn the vision into reality. This is where we can discuss the context of a directory (LDAP) based infrastructure further.

An enterprise infrastructure is a collection of user accounts, groups, computers and other resources that share a common security boundary. Within that boundary, architects and system engineers must establish an environment that insures security and provides a concept known as least privilege. Least privilege and least rights means that any user has only those rights required for him or her to do their jobs and no more.

Directory based management does not always provide a common security boundary or the ability to lock down least privilege within the boundary. I look at Novell as a company with the tools necessary to provides an entire infrastructure with a common security boundary. But, Open Enterprise Server (OES) and Open Workgroup Suite are products for knowledge workers does not an enterprise make.

We can also vary for a moment from the enterprise and go right down to the local Linux PC. We could say that the lack of lock down policies at the local level are missing too. Also, where in the collection of computers users and accounts that would make up common security boundary does an administrator have the ability to provide a hierarchical set of policies that can carry through and override local and/or workgroup policies.Without that structure you can have an organization running amuck.

Going forward in the LDAP series, I want to tease out a theoretical model out further. We can call it a blue print, if you would like. It's an idea, in my opinion, whose time has come.

In this blog entry, I just wanted to make you aware of the possibilities.

__________________________


Special Magazine Offer -- Free Gift with Subscription
Receive a free digital copy of Linux Journal's System Administration Special Edition as well as instant online access to current and past issues. CLICK HERE for offer

Linux Journal: delivering readers the advice and inspiration they need to get the most out of their Linux systems since 1994.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Anonymous's picture

Just to be sure:

On October 13th, 2007 Anonymous (not verified) says:

Just to be sure:
LDAP - lightweight directory access potocol, right?

Josiah's picture

Group Policy

On January 3rd, 2007 Josiah (not verified) says:

I think something that touches on what you are talking about is group policy. The management capabilities related to group policy in AD is what eventually caused our switch from LDAP to AD. I'd like to see LDAP capable of handling that sort of thing easily and across platforms.

kr_line's picture

eDirectory and LDAP

On January 3rd, 2007 kr_line (not verified) says:

We are using Novell Netware since more then 10 years in our world-wide company WAN. eDirectory is a GREAT advantage for ease of user rights management. With Novell moving slowly but steadily to Linux, we are looking forward to a more tightly integration of eDirectory (or LDAP) into Linux. Once a centralised and company-wide user-rights and security management is integrated with the distribution, this could be the most important leap forward for Linux to become the OS of choice for large companies.

Post new comment

Please note that comments may not appear immediately, so there is no need to repost your comment.
The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <pre> <ul> <ol> <li> <dl> <dt> <dd> <i> <b>
  • Lines and paragraphs break automatically.

More information about formatting options

Newsletter

Each week Linux Journal editors will tell you what's hot in the world of Linux. You will receive late breaking news, technical tips and tricks, and links to in-depth stories featured on www.linuxjournal.com.
Sign up for our Email Newsletter

Tech Tip Videos

From the Magazine

July 2009, #183

News Flash: Linux Kernel 3.0 to include an on-the-go Expresso machine interface! Ok, maybe not, but Linux is definitely going mobile, from phones to e-readers. Find out more inside about Android, the Kindle 2, the Western Digital MyBook II, The Bug, and Indamixx (a portable recording studio). And if you've gone mobile and you been wanting more Emacs in your life then check out Conkeror.


To compliment the mobile we've got the stationary: parsing command line options with getopt, checking your Ruby code with metric_fu, and building a secure Squid proxy. How is this stationary you ask? What can we say? It's not. We just wanted to see if anybody actually read this part of the page :) .


All this and more, and all you have to do is get your hot sweaty hands on the latest copy of Linux Journal.





Read this issue