This is a second attempt to send this message to the
per...@li... list. It appears
that the first message got lost somewhere.
Attached are 4 patch files that hopefully will fix
several concerns about the perl-ldap module's ability
to pull schema information correctly. These patch files
were generated from version .22.
I have tested these changes against my Openldap 2.0.7
server, my x.500 servers, and Netscape 4.x server.
There were no problems pulling the schema or rootDSE
information.
I have not had a chance to test this against an Exchange
server or Active Directory server. I hopefully will be
able to do this in the very near future.
I have not tested the functions that decode matchingRuleUse,
dITStructureRules, dITContentRules, or nameForms because I
do not have access to any servers that have these structures.
About the patch files.
LDAP.pm.patch -> I modified the schema function to use the
correct filters and added the attrs option to retrieve all of
the attributes associated with the rootDSE and subschemaSubentry.
LDAP.pod.patch -> I added documentation about the schema function
and root_dse function. I added examples to show how to use
the schema function to retrieve objectClasses and attributes.
Once these are understood pulling the other attributes
(matchingRules, etc) is easy to do.
I added examples to show how to use the root_dse function and
how to use the get_value method to retrieve rootDSE attribute
information.
Schema.pm.patch -> I added code to comprehend the
matchingRuleUse, dITStructureRules, dITContentRules,
nameForms attributes.
Schema.pod.patch -> I added documentation on the functions
that determine object type and retrieve attribute data for
matchingRuleUse, dITStructureRules, dITContentRules,
nameForms attributes.
Regards,
Clif Harden ch...@po... |
