Ugh. Don’t you just hate it when things don’t work as expected?
So, after finally mastering the “new” version of Net::LDAP::Schema it was time to turn it on Oracle Internet Directory.
[eldapo@testguy tools]$ ./schemaparse.pl
Cannot parse [( 1.3.6.1.1.1.1.22 NAME 'macAddress' DESC 'MAC
address in maximal, colon separated hex notation,
eg. 00:00:92:90:ee:e2' EQUALITY caseIgnoreIA5
Match SYNTAX '1.3.6.1.4.1.1466.115.121.1.27'{128} )]
{{128}} at /usr/lib/perl5/vendor_perl/5.8.8/Net/LDAP/Schema.pm
line 351, line 225.
...propagated at ./schemaparse.pl line 14, line 225.
Looks to me like a malformed schema element. Why am I surprised?
Which kind of explains now why phpldapadmin has such trouble browsing an Oracle directory (php’s LDAP code owes more to Net::LDAP than many realize).
Wonder what impact this might have on other 3rd party apps (do I really have to ask?).
Big shout out to Oracle developers: Please see RFC 4511 and related Internet standards, as revised, for LDAP Protocol version 3, and conform your software as required.
So here’s where I get out my LDAP software entrenching tool and go to work on the OID schema.
Stay tuned for my next report …