We are sure :) Unless we want to write a plugin to Artemis that wraps the connection in
H-Accounts so we can secure it.
Do we make sure that the bus is only visible internally then
(e.g. only binding to management interface)?
No. That was always something that needed to get done. We need to secure the bus using the
out-of-box security or write a plugin so we can put accounts security around it. I
don't know of a way to make sure the bus is visible internally across servers.
Remember, yeah, today, we are always using a single instance of Hawkular Server (with one
instance of alerts and inventory and metrics) but that isn't the interesting
deployment scenario (really, we don't need a bus if that's all we care about - we
couldn't done this stuff much easier without it:. As soon as we introduce two servers,
then we can't just bind to 127.0.0.1 (though we could bind to management address, but
then i always thought that was mainly to bind to the local IP).
----- Original Message -----
> Hey,
>
> while I am pretty sure we said we do not want to receive data
> (Metrics, Inventory) from outside Hawkular via Bus, I wanted to
> make sure anyway.
>
Do we make sure that the bus is only visible internally then
(e.g. only binding to management interface)?
>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hawkular-dev
>