Working With Oracle® Solaris 11.2 Directory and Naming Services: LDAP

Exit Print View

Updated: July 2014
 
 

Avoiding Server Timeouts With Oracle Directory Server Enterprise Edition

When the N2L server refreshes a map, the result might be a large LDAP directory access. If the Oracle Directory Server Enterprise Edition is not correctly configured, the refresh operation might time out before completion. To avoid directory server timeouts, you must modify Oracle Directory Server Enterprise Edition attributes manually or by running the idsconfig command.

For example, to increase the minimum amount of time in seconds that the server should spend performing the search request, modify these attributes:

dn: cn=config
nsslapd-timelimit: -1

For testing purposes, you can use an attribute value of –1, which indicates no limit. When you have determined the optimum limit value, change the attribute value. Do not maintain any attribute settings at –1 on a production server. With no limits, the server might be vulnerable to Denial of Service attacks.

For more information about configuring Oracle Directory Server Enterprise Edition with LDAP, see Chapter 4, Setting Up Oracle Directory Server Enterprise Edition With LDAP Clients of this book.