Directory Services as the Foundation of Organizational Infrastructures
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.
|Designing Electronics with Linux||May 22, 2013|
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
- Designing Electronics with Linux
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Dynamic DNS—an Object Lesson in Problem Solving
- Using Salt Stack and Vagrant for Drupal Development
- Why Python?
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Validate an E-Mail Address with PHP, the Right Way
- What's the tweeting protocol?
- Tech Tip: Really Simple HTTP Server with Python
2 hours 8 min ago
- Kernel Problem
12 hours 10 min ago
- BASH script to log IPs on public web server
16 hours 38 min ago
20 hours 13 min ago
- Reply to comment | Linux Journal
20 hours 46 min ago
- All the articles you talked
23 hours 9 min ago
- All the articles you talked
23 hours 12 min ago
- All the articles you talked
23 hours 14 min ago
1 day 3 hours ago
- Keeping track of IP address
1 day 5 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?