Applies to: All versions of Centrify ldapproxy
When requesting data of using the pagedResult control, it works without any error. However if the control is made to be critical it returns a "Critical control unavailable in context" error.
For example, the following query works:
ldapsearch -x -h localhost -b dc=example,dc=com -D firstname.lastname@example.org -E 'pr=50' -W '(objectClass=posixAccount)
However it fails when making it critical:
ldapsearch -x -h localhost -b dc=example,dc=com -D email@example.com -E '!pr=50' -W '(objectClass=posixAccount)
As of Centrify Suite 2018, Centrify ldapproxy does not support "!" (Critical search extension). An enhancement request has been filed and we will update the ETA for this feature once available.