279172 - I need help in using simple Paged Result LDAP Control.

Status: RESOLVED INVALID

(Directory :: LDAP C SDK, defect)

Description

[Kiran Singh]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Build Identifier: 

We have a program that does ldap search with the paged result control against a 
directory server. This directory server (Secureway directory) does support the 
paged control but has been configured to allow only the root account to run 
this type of search.  So when our program runs as the other user, we get 
ldaperr 50 (insufficient access) from the server but a regular search (without 
the page control) runs fine. My questions:

1. Does the server returns the result set with this error?
2. Do you have a documentation on how to use this type of control like the one 
on server-side sorting control in the Mozilla LDAP C SDK programmers' guide?
3. As a possible solution to fix this problem, I can try to make sure that the 
server supports the page control by using the method in the programmers's 
guide, before I do the ldap search with the page control otherwise I will do 
the normal search.
My question is, would the server be able to tell me if it supports or not 
depending on the user I am connected as ?

I will appreciate any information on this topic.
Thanks
Kiran

Reproducible: Always

Comment 1

[Kiran Singh]

I want to add that we didn't mark the page control as "Critical".

Comment 2

[Mark Smith [:mcs]]

I do not see a Mozilla LDAP C SDK bug here although perhaps our documentation
can be improved ;-)

If you are really using the Simple Paging Control (RFC 2696), you likely already
know that our SDK has no special support for that control.  I personally do not
have any experience with it and the Secureway DS, but using any LDAP control
should be similar to using any other LDAP control.

If a control is not marked critical, servers usually will ignore the control if
they do not support it.  But they may very well return "access denied" for a
control they support, even if it is not marked critical.  So you will probably
need to probe to determine whether the control is supported.  Unfortunately, the
supportedControl attribute in the LDAP root DSE is usually the same regardless
of who is asking (although it is possible Secureway acts differently).  It might
be best to try to use the control and them remember whether it is supported or
not for a particular user (whether that approach is convenient or not depends a
lot on how your LDAP client application is structured).

Comment 3

[Mark Smith [:mcs]]

Resolving as Invalid.  Please send me private email if you have additional questions, or post on one of the LDAP newsgroups or mailing lists.