apache
WIP: AMQ-9627 Don't fail on start if cachedLDAPAuthorizationMap is used and the LDAP server is not available.
What problems does this PR solve? it fixes a crash on start if cachedLDAPAuthorizationMap is used and the LDAP server is not available.
Why is it beneficial to merge into ActiveMQ? it's rather inconvenient, as cachedLDAPAuthorizationMap is usually used to avoid issues with the LDAP server being not always available
How do you make sure this PR is well tested? I added a test that reproduces the error without the change.
Question @Nikita-Shupletsov, once the user fixed the issue with the configuration or their LDAP server, does the user need to restart the server? In another word, is this code part of the code path that get triggered everytime the broker performs AuthN/AuthZ?
If that latter case is true, the activemq.log be flooded with error message. How do we make it less noisy?
Question @Nikita-Shupletsov, once the user fixed the issue with the configuration or their LDAP server, does the user need to restart the server? In another word, is this code part of the code path that get triggered everytime the broker performs AuthN/AuthZ?
If that latter case is true, the activemq.log be flooded with error message. How do we make it less noisy?
No, they will not need to. afaik, that's the whole idea of this Cached Map is to be able to withstand connection failures. it will try to fetch data on every request until is succeeds