ldapRegistry-3.0 does not configure a read timeout for JNDI connections #3383
Labels
release bug
This bug is present in a released version of Open Liberty
release-18.0.0.2
team:Wendigo East
The ldapRegistry-3.0 feature does not allow the user to configure, nor does it configure implicitly a read timeout on the JNDI context. This can lead to hangs when an LDAP server does not respond.
Set the read timeout either based on the connect timeout that is already exposed or add a separate read timeout. This value should align closely with the "searchTimeout" used on the SearchControls as the time limit for a search operation.
The text was updated successfully, but these errors were encountered: