Hi Aleksandr,

the JIRA ARTEMIS-4582[1] should also cover the use case of config reload
and and the related PR was created 2 days ago:
https://github.com/apache/activemq-artemis/pull/4820

[1] https://issues.apache.org/jira/browse/ARTEMIS-4582

Regards,
Domenico

On Thu, 15 Feb 2024 at 16:21, MILOVIDOV Aleksandr
<aleksandr.milovi...@raiffeisen.ru.invalid> wrote:

> Hi Team,
>
> Currently we have ActiveMQ Artemis broker where access to management
> console is granted for several user teams with different permissions.
> Permissions are granted for LDAP groups.
> For example, we grant ApplicationA developers/testers/operations users
> permissions to work with addresses APP.A.* (and its corresponding DLQ),
> ApplicationB team - APP.B.* addresses, and both teams to common addresses
> like APPS.A.B.*.
>
> Sometimes we need to add, change or remove permissions because new team or
> new application was created, or team was separated to several
> feature-teams, or something else was changed. And it is impossible to apply
> changes without interruption of service. We can change permissions, but it
> needs restart of Artemis to make new permissions work.
>
> Is it possible to create Jira task which is some kind of new feature
> request or improvement request to make possible reloading permissions from
> management.xml ?
> And is there any chance that it can be implemented?
>
> --
> Best regards,
> Aleksandr
>
>
> -----------------------------------
>
> This message and any attachment are confidential and may be privileged or
> otherwise protected from disclosure. If you are not the intended recipient
> any use, distribution, copying or disclosure is strictly prohibited. If you
> have received this message in error, please notify the sender immediately
> either by telephone or by e-mail and delete this message and any attachment
> from your system. Correspondence via e-mail is for information purposes
> only. AO Raiffeisenbank neither makes nor accepts legally binding
> statements by e-mail unless otherwise agreed.
>
> -----------------------------------
>

Reply via email to