It seems that a Destinations SecurityConfig is never transferred to the other nodes in the
cluster,
leaving the destination wide open or unusable depending on the DefaulSecurityConfig of the
ServerPeer.
Unless I have missed something, this is probably a bug and not by design.
Should I add a Jira case ?
I could start working on it if wanted..
Should be as 'simple' as getting the qeues SecurityMetaData from the deploying
ServerPeer,
sending it as part of the MappingInfo, and adding it to the receiving ServerPeer.
-aslak-
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083892#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...