I agree, it’s the best choice make it configurable on acceptor bases.
I’ll take a look to your pr.
Thank you a lot!
> Il giorno 19 dic 2019, alle ore 17:28, Justin Bertram
> ha scritto:
>
> After thinking about this a bit more it made more sense to me for the
> plugin to be defined on a per-a
After thinking about this a bit more it made more sense to me for the
plugin to be defined on a per-acceptor and per-connector basis. Therefore I
made the configuration part of the broker & client URLs via the new
"trustManagerFactoryPlugin" parameter. I opened a JIRA [1] and sent a PR
[2].
Justi
I think this idea has merit, especially considering it's something that the
5.x code-base supports. There are lots of bits of pluggable functionality
in Artemis (e.g. metrics [1], security settings [2], etc.). This could
follow the same pattern where the plugin could be defined in broker.xml
with a
Hello,
I have some security (SSL stack and ACLs) related use cases that seem
to be not implemented in Artemis code.
For example I need to plug a custom X509TrustManager on Artemis broker
acceptors. After looking at the source code I think I found a way:
https://github.com/riccardomoda
