-
Story
-
Resolution: Done
-
Major
-
None
-
False
-
None
-
False
-
Compatibility/Configuration, User Experience
-
-
+
When using the PropertiesLoginModlue and after an ActiveMQArtemisSecurity object is updated a full StatefulSet rollout takes place. It would be more ideal if the CLI could be use from the operator so that changes are applied immediately without a restart.
Additionally, the ACLs defined in the `security-settings` could just be updated with a certain refresh-period.
This not only benefits any type/size of deployments but also makes the user experience closer to Keycloak integrations
- depends on
-
ENTMQBR-6773 Provide feedback on the results of applying spec.brokerProperties
- Closed
-
ENTMQBR-6980 properties config - allow role configuration
- Closed
-
ENTMQBR-6983 properties config - treat url with / as directory of alphabetically ordered <..>.properties files
- Closed
- incorporates
-
ENTMQBR-5713 Request to allow multiple ActiveMQArtemisSecurity CRs in AMQ 7
- Closed
-
ENTMQBR-5144 Support for more login modules in security config
- Closed
-
ENTMQBR-7447 KeycloakLoginModule's configuration credentials should have an option to store the client-secret in an Openshift secret.
- Closed
- is cloned by
-
ENTMQBR-7525 Support JAAS config via extra mount config map reference
- Closed
- is related to
-
ENTMQBR-3606 AMQ 7 Operator : provide way to configure the LDAP for authentication
- Closed
-
ENTMQBR-4468 Encrypting amq broker pod credentials from env variables
- Closed
-
ENTMQBR-5203 Create Custom Resources variables to overwrite StatefulSet environment variables or JVM options
- Closed
- relates to
-
ENTMQBR-7819 [Docs] Clarify what the status means for brokerProperties and JAAS properties login modules
- Closed