Release Notes › Policy Server Release Notes › Defects Fixed in SiteMinder Releases › Defects Fixed for 6.0 SP1 › Configuring a Time Delay for Rebinding Attempts in LDAP Directories (30640, 30534, 30647)

Configuring a Time Delay for Rebinding Attempts in LDAP Directories (30640, 30534, 30647)

When the Policy Server is using Active Directory as a user store over LDAP (using the AD namespace), the LDAP connections are frequently "Marked Close Pending". The Policy Server thread or ping server thread waits or sleeps for 5 seconds after a connection is Marked Close Pending and attempting to bind a new connection.

Users can configure a new registry setting 'BindLDAPServerDelay' in seconds to determine the amount of delay required before attempting to rebind to an LDAP server.

To set this registry value

Windows

1. From the Windows Start menu, select Run.
2. Enter regedit in the Run dialog box and click OK.
3. In the Registry Editor, navigate to:

   \HKEY_LOCAL_MACHINE\SOFTWARE\Netegrity\SiteMinder\CurrentVersion\Ds\LDAPProvider
   

4. Create or modify the following BindLDAPServerDelay registry key and set the value that you want in seconds. The key must be of the type REG_DWORD.

Note: If you do not manually configure this setting on the machine where the Policy Server.

UNIX

1. Navigate to <install dir>/siteminder/registry
2. Open sm.registry in a text editor.
3. Locate the following text in the file:

   \HKEY_LOCAL_MACHINE\SOFTWARE\Netegrity\SiteMinder\CurrentVersion\Ds\LDAPProvider
   

4. Locate the line that follows the line from step 3 and begins with:

   BindLDAPServerDelay

5. Create or modify the following BindLDAPServerDelay registry key and set the value that you want in seconds.

Note: If you do not manually configure this setting on the machine where the Policy Server installed, then the Policy Server waits for 5 seconds, the default value.