-
Story
-
Resolution: Unresolved
-
Major
-
None
-
AMQ 7.9.1.GA
-
None
-
False
-
None
-
False
-
Release Notes, User Experience
-
A customer has observed many requests (maxed to 20 by default in the keycloakLoginModule.configuration.connectionPoolSize operator parameter https://access.redhat.com/documentation/en-us/red_hat_amq/2021.q3/html-single/deploying_amq_broker_on_openshift/index#security-crd-reference_broker-ocp) being sent to Keycloak at the same time.
AMQ should not send all these requests parallel, but it should have a smarter caching implementation, to send only one requests to Keycloak to refresh the cache and return the old cached value until this call is complete, see current implementation in
The AMQ-SSO integration should be enhanced to avoid serious problems caused by a slow authentication provider.
- is incorporated by
-
ENTMQBR-1828 Support for generic OAuth based authentication-authorization in AMQ (non keycloak)
- To Do
- relates to
-
ENTMQBR-3606 AMQ 7 Operator : provide way to configure the LDAP for authentication
- Closed