OID 10g ldapsearch With -X Flag Returns Incorrect And/Or Inconsistent Results For Attributes With Base64 Encoded Values
(Doc ID 1407515.1)
Last updated on FEBRUARY 26, 2019
Applies to:Oracle Internet Directory - Version 10.1.4 to 10.1.4.3 [Release 10gR3]
Information in this document applies to any platform.
Oracle Internet Directory (OID) 10g.
Running ldapsearch with -X flag (print entries in XML format) where a attribute is stored with base64 encoding, results are incorrect and/or not consistent.
This affects scripts that make use of ldapsearch -X, such xmlparserv2.jar for xml file parsing, which returns error:
For example, for attribute "a" with a base64 encoded value, an ldapsearch without -X shows correctly:
But ldapsearch with -X, the "a" attribute value shows differently and can change every time the ldapsearch is rerun:
The difference may be noticeable or it may be subtle such as an extra non-printable character at the end of the value.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document