LDAP: Attributes and Keeping Them Simple
A consensus exists among many writers about jargon. Throw a bunch of undefined words at a reader and he or she will soon fall asleep. In fact, put one term in a paragraph that the reader doesn't understand and a page or two later sleep will start to creep and the reader will lose interest.
So, in spite of the what many technical writers practice, I thought I might give you a break. You don't need to know everything about LDAP directory components or the construction of an address book to begin understanding the technology behind directories.
To a person who wants to find the name and email address of someone, he or she wants to do a simple search to find it. Does that person need to know how the information got into the directory? Do they need to understand how the directory came into being? Think about that.
In Gerald Carter's book, "LDAP Administration", he addresses attributes in a way I find intimidating. Here's a little quote for you:
Attributes types and the associated syntax rules are similar to variables and data type declarations found in many programming languages. The comparison is not that big a stretch.
OK then. How about another way of discussing it. Attributes hold information you need in a directory. For example, they might contain someone's name, address, telephone numbers, employee numbers, the department in which he or she work, his or her job title, etc.
Many other attributes exist in directories and LDAP administrators organize those attributes using something we will discuss in the next installment.
So, get ready for the next bit of jargon called objectClasses. You should find that subject pretty interesting if I can manage to write about it without putting you into an altered state.
Fast/Flexible Linux OS Recovery
On Demand Now
In this live one-hour webinar, learn how to enhance your existing backup strategies for complete disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible full-system recovery solution for UNIX and Linux systems.
Join Linux Journal's Shawn Powers and David Huffman, President/CEO, Storix, Inc.
Free to Linux Journal readers.Register Now!
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
- Chris Birchall's Re-Engineering Legacy Software (Manning Publications)
- The Italian Army Switches to LibreOffice
- Linux Mint 18
- Petros Koutoupis' RapidDisk
- ServersCheck's Thermal Imaging Camera Sensor
- Oracle vs. Google: Round 2
- The FBI and the Mozilla Foundation Lock Horns over Known Security Hole
- Privacy and the New Math
Until recently, IBM’s Power Platform was looked upon as being the system that hosted IBM’s flavor of UNIX and proprietary operating system called IBM i. These servers often are found in medium-size businesses running ERP, CRM and financials for on-premise customers. By enabling the Power platform to run the Linux OS, IBM now has positioned Power to be the platform of choice for those already running Linux that are facing scalability issues, especially customers looking at analytics, big data or cloud computing.
￼Running Linux on IBM’s Power hardware offers some obvious benefits, including improved processing speed and memory bandwidth, inherent security, and simpler deployment and management. But if you look beyond the impressive architecture, you’ll also find an open ecosystem that has given rise to a strong, innovative community, as well as an inventory of system and network management applications that really help leverage the benefits offered by running Linux on Power.Get the Guide