Community Articles
Find and share helpful community-sourced technical articles
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.
Labels (1)
Rising Star

OBJECTIVE:

Resolve issues with some lightweight LDAP services such as the HDP Demo LDAP Provider


OVERVIEW:

Some LDAP services do not properly support paging for LDAP query results. In order to support these LDAP services, paging of results needs to be disabled in the LDAP provider properties for the NiFi Registry service


SYMPTOM:

The NiFi Registry does not respond or times out, and the following error is seen repeatedly in the NiFi Registry log (nifi-registry-app.log):

2018-09-01 01:01:05,189 INFO [main] o.s.l.c.AbstractRequestControlDirContextProcessor No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl
2018-09-01 01:01:05,274 INFO [main] o.s.l.c.AbstractRequestControlDirContextProcessor No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl
2018-09-01 01:01:05,359 INFO [main] o.s.l.c.AbstractRequestControlDirContextProcessor No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl

RESOLUTION:

Using Ambari, under the configs tab for NiFi Registry, navigate to the Advanced nifi-registry-authorizers-env section.

Edit the "Template for authorizers.xml" value to remove the Page Size property. Removing this property will disable paging for LDAP queries in this identity provider. Be aware that for extremely large result sets, this can result in a connection timeout.

89391-nifi-reg-ldap-page.png

After saving the change, restart the Nifi Registry service.

374 Views
0 Kudos
Don't have an account?
Coming from Hortonworks? Activate your account here
Version history
Revision #:
2 of 2
Last update:
‎08-17-2019 06:27 AM
Updated by:
 
Contributors
Top Kudoed Authors