September 11, 2017 at 1:43 pm #18830tniebuhrParticipant
openDJ Version 3.0 (mandatory version to be used on customer side)
We have an external application that needs to query the external changelog (cn=changelog). For that, we have created a dedicated account to be used, which works fine: I can see all changes and can also query the changenumbers I need to fetch.
However, this does only work with regular searches, but not when using simplePageSize control (OID 1.2.840.1135220.127.116.119), which is what the external application is doing as well.
example (simplified the logs):
working example without using paged searches
./ldapsearch -D “cn=dedicated_user” -w password -s sub -b cn=changelog “(cn=*)” connection
./ldapsearch -D “cn=dedicated_user” -w password -s sub -b cn=changelog –simplePageSize 50 “(cn=*)” connection
SEARCH operation failed
Result Code: 12 (Unavailable Critical Extension)
Additional Information: The search request cannot be processed because it contains a critical control with OID 1.2.840.113518.104.22.1689 that is not supported by the Directory Server for this type of operation
using the paged search on ‘standard user context’ (eg dc=whatever) works fine.
So the question: how to enable pagedSearch on cn=changelog ? using ‘targetcontrol’ on cn=changelog (entry as ACI) seems not be possible?!
And yes: the same happens with cn=Directory Manager and on freshly installed server without any special ACI settings.
ThorstenSeptember 11, 2017 at 2:14 pm #18831JnRouvignacParticipant
The changelog backend does not support the paged results control, thus any use of the paged result control will be ignored.
However, if you are relying on the
changenumberattribute, you can already emulate page result control by using range filters.
For example, let’s say the last
5719, in this case you can ask for the next hundred changenumbers with the search filter
- This reply was modified 2 years, 11 months ago by JnRouvignac.
You must be logged in to reply to this topic.