AMQ 7 LDAP Connectivity errors and login cache

Solution Verified - Updated -

Issue

When a temporary LDAP connectivity issue occurs, the LDAP local cache retains a failed authentication attempt for a client. For example, the following connectivity exception:

AMQ224084: Failed to open context: javax.naming.CommunicationException: ldap.host.com:3269 [Root exception is java.net.ConnectException: Connection timed out: connect]

results in a failed authentication attempt to be cached locally; clients are not able to authenticate even after the LDAP connectivity issue is resolved. This is particularly apparent with a high security-invalidation-interval. The cache will not be refreshed until after the security-invalidation-interval time has been exceeded.

Environment

  • Red Hat AMQ
    • 7.10

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content