On Thu, Nov 4, 2010 at 3:53 PM, Ted Unangst <ted.unan...@gmail.com> wrote: > On Thu, Nov 4, 2010 at 3:10 PM, Adam M. Dutko <dutko.a...@gmail.com> wrote: >>> I can't really comment on the accuracy because I'm trying to avoid >>> learning about LDAP at all cost, but this gives me enough info to >>> start searching with, so I think it's a great addition. >>> >> >> What is the technical reason behind not wanting to learn about LDAP? I'd be >> interested to hear feedback/input from you and the rest of the list.
On second thought, I should answer with a little less snark, though I think this one attribute sums it up pretty well. First, some committee sat around and tried to come up with all the things needed to describe a person, like license plates and pager numbers and who your secretary is. It's like it's custom built for handling the personnel records of IBM management. They made all this nonsense optional thankfully, but who's to say there aren't other attributes you need to store in your organization? Now you're off making your own schema. Adios interop! Second, the file formats seem purpose designed to be incomprehensible. Third, just doing something as simple as putting a single user record into the db using ldapadd involved an insane amount of typing of magic incantations. This is not entirely the tool's fault, there's just so much "stuff" involved it bubbles up to the user whether they like it or not. On the whole, "infinite flexibility" is pretty much synonymous with "infinite complexity". > attributetype ( 2.16.840.1.113730.3.1.1 > NAME 'carLicense' > DESC 'RFC2798: vehicle license or registration plate' > EQUALITY caseIgnoreMatch > SUBSTR caseIgnoreSubstringsMatch > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
