You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2022/11/29 19:18:00 UTC

[jira] [Updated] (ARTEMIS-4101) SecurityStore caches failed authentication result from LDAP connection failures

     [ https://issues.apache.org/jira/browse/ARTEMIS-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram updated ARTEMIS-4101:
------------------------------------
    Description: 
If the LDAP infrastructure temporarily becomes unavailable, the broker caches the failure and no longer attempts to authenticate/authorize the user. This is a problem in use-cases with the {{security-invalidation-interval}} configured to a longer time period.

Desired behavior - if the LDAP infrastructure has a connectivity problem, the broker should attempt to authenticate on subsequent logins rather than caching the result of the failure.


> SecurityStore caches failed authentication result from LDAP connection failures
> -------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-4101
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4101
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>            Priority: Major
>
> If the LDAP infrastructure temporarily becomes unavailable, the broker caches the failure and no longer attempts to authenticate/authorize the user. This is a problem in use-cases with the {{security-invalidation-interval}} configured to a longer time period.
> Desired behavior - if the LDAP infrastructure has a connectivity problem, the broker should attempt to authenticate on subsequent logins rather than caching the result of the failure.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)