Graham, The code in schema.pm worked great! However the schema function in ldap.pm does not ask for the extendedattributeinfo attribute. I had to do a manual ldap search and create a schema object based on that..
I'm not sure if this is by design or will this all this just work in the next version of Net::LDAP? Thoughts? Thanks E. On Fri, December 22, 2006 2:31 pm, Graham Barr wrote: > On Dec 6, 2006, at 8:02 AM, Eric Nichols wrote: >> Excuse all of my past ramblings about schema... >> >> Active Directory (and possibly ADAM) stores extended attribute schema >> information in extendedAttributeInfo. I wrote a function which >> merges this >> information with attributeTypes. Each extended attribute will be >> prefixed >> with an 'x-' in keeping with some much needed guidance from Peter >> Marschall. >> >> The result is a merged Net::LDAP::Schema object with some important >> information such as attribute length and if it is indexed etc. >> >> Is this a hack? Absolutely. >> >> Is extentedattributeinfo LDAP standard? Nope, But I have seen it >> implemented >> in Active Directory, ADAM and even seen mention of it in Lotus Notes. >> >> My hope is that someone can carry this code on into a sub class >> (Net::LDAP::Schema::Extended?). I have only tested this code in so >> far as >> reading attribute information. I have not played with any other >> Schema >> functions with this hacked object. > > Eric, > > Thanks for the code and sorry for the slow reply. > > I personally do not like the idea of subclassing this. Just because > some people do not follow standards in no reason to not try to > support in the best possible manner. > > I agree with prefixing them with x- into attribute types. Servers > which support extendedAttributeInfo probably do not use x- in > attribute types anyway. However I have attached an alternate patch I > would like you to try. > > Graham. >
