Hello,
We recently switched from JNDI to UnboundID LDAP SDK for Java (https://www.ldap.com/) for LDAP requests to Oracle Internet Directory (OID) LDAP Server. We got paged search problem with Oracle OID LDAP Server that we didn’t have while using JNDI.
Looking at the trace with OID LDAP Server, WireShark clearly displays error in OID encoding of reply to paged search request: "BER Error: This filed lies beyond the end of the known sequence definition. BER Error: Unknown field in Sequence"
As a result, UnboundID LDAP library does NOT return cookie for next page request.
We confirmed from network traces and contacting UnboundID (https://sourceforge.net/p/ldap-sdk/discussion/1001257/thread/ecb0415f/ ) that the problem is in Oracle OID LDAP Server – incorrect encoding reply to paged search request.
There are other references to the same problem from different sources, for example http://www.nntp.perl.org/group/perl.ldap/2012/01/msg3574.html
Response returned by the OID server is malformed. The short explanation is that OID is incorrectly placing the response control inside the search result done protocol op element of the LDAP message instead of the portion of the LDAP message where controls are supposed to go. This is a result of a single-byte error in the response.
Please look here for more detailed explanation: https://sourceforge.net/p/ldap-sdk/discussion/1001257/thread/ecb0415f/
We tried with
Oracle Internet Directory 11g R1 (11.1.1.9 my testing environment)
Oracle Internet Directory 11g R1 (11.1.1.5 customers' environment)
Is it known problem?
Is any fix exist that can be applied to OID?
Thanks in advance,
Sergey Klyushin