Great news, thank you!
> Il giorno 11 dic 2019, alle ore 20:48, Justin Bertram
> ha scritto:
>
>> Currently there is no way to use a custom ActiveMQSecurityManager
> implementation via the XML configuration.
>
> FYI - I just opened ARTEMIS-2574 [1] and sent a PR [2] to address this.
>
>
>
> Currently there is no way to use a custom ActiveMQSecurityManager
implementation via the XML configuration.
FYI - I just opened ARTEMIS-2574 [1] and sent a PR [2] to address this.
Justin
[1] https://issues.apache.org/jira/browse/ARTEMIS-2574
[2] https://github.com/apache/activemq-artemis/pull
> In few word what I’d like to achieve is to let Artemis instantiate and
use a custom ActiveMQSecurityManager provided through a configuration
parameter. Is there a way or I must patch the Artemis code to allow the
ActiveMQSecurityManager pluggability?
Currently there is no way to use a custom Act
Hi, unfortunately I cannot rely on a security repository and the users and ACLs
profiles could be thousands.
My idea is to replace the ActiveMQJAASSecurityManager with my own custom
ActiveMQSecurityManager implementation.
But I didn’t find a way.
It seems that there is no other way than specifyi
Yes, it would check every time a client publishes a message or subscribes
an address.
>From my understanding, SecuritySettingPlugin should meet your requirements.
You can save the "securityRepository" passed by "SecuritySettingPlugin::
setSecurityRepository" in your custom SecuritySettingPlugin. W
I think the SecuritySettingPlugin will not solve my issue but an
ActiveMQSecurityManager3 custom implementation could be.
So I tried to plug an ActiveMQSecurityManager3 implementation but without any
success.
From my understanding this plugin should be defined into bootstrap.xml but
unfortunate
You might need to write some custom code to do what you want and you could
try a custom Security plugin.
See the API and Java docs for the security setting plugin:
https://github.com/apache/activemq-artemis/blob/master/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/SecuritySet
I already read this page and I wasn’t able to find any helpful information.
In our use case each user has ACL depending on the username itself. Moreover a
user can be added at runtime and the broker must be able to create and handle
correctly the ACL also for the new created user.
So, at the end
All of the info you should need to get started should be here:
https://activemq.apache.org/components/artemis/documentation/latest/security.html
On Mon, Aug 26, 2019 at 6:24 AM Modanese, Riccardo
wrote:
> Hello,
> In our ActiveMQ 5.x security plugin code we are enforcing ACL
> programmatical
Hello,
In our ActiveMQ 5.x security plugin code we are enforcing ACL
programmatically so I’m investigating how to migrate our current ACL from
ActiveMQ 5.x to Artemis.
I took a look into Artemis source code and I didn’t find any similar object to
those present in ActiveMQ 5.x (E.g.
org.apa
10 matches
Mail list logo
