Thanks Tim - I think I’ve got one working now. I wound up casting the result of getConnector() to TransportConnector and then calling getName() - it looks like it has what I need.
I’ve got a version running locally now, and it seems to be doing what I’m after. Thanks for all of your help. BTW - let me know if you think this is something the community would like and I’ll put together a PR for it. Thanks Again Quinn > On Mar 25, 2018, at 11:11 PM, Tim Bain <tb...@alumni.duke.edu> wrote: > > Quinn, > > I think you should be able to access the URI to which the connection is > bound by calling > ((TransportConnector)context.getConnector()).getServer().getConnectURI(), > and then you can parse the protocol out of it. But it's not something I've > personally done and I don't have time to try it right now, so this is > purely conjecture based on the documentation plus reading the code. So if > that doesn't work, I apologize, but let me know how it blows up and I can > try to help further. > > Tim > > On Thu, Mar 22, 2018 at 10:22 AM, Quinn Stevenson < > qu...@pronoia-solutions.com> wrote: > >> Thank you Tim - >> >> I was afraid you were going to say that :-) >> >> I was looking at the SimpleAuthenticationPlugin / >> SimpleAuthenticationBroker, and I have an idea how to do this. The one >> thing I’m not sure about is how I can tell when the connection is coming >> via a VM URL - do you have any hints on that? >> >> >>> On Mar 21, 2018, at 7:21 PM, Tim Bain <tb...@alumni.duke.edu> wrote: >>> >>> I'm not sure there's a built-in way to do this without writing any code, >>> but you should be able to write a simple security plugin that allows you >> to >>> allow or deny connections based on their transport and whether they are >>> anonymous. The bottom of http://activemq.apache.org/security.html has >>> details about how to get started. >>> >>> Tim >>> >>> On Wed, Mar 21, 2018, 6:08 PM Quinn Stevenson < >> qu...@pronoia-solutions.com> >>> wrote: >>> >>>> I have several components running inside the same JVM as ActiveMQ, and >>>> they connect to the broker using a vm URL. Guest access to the broker >> has >>>> been disabled for security reasons, but I’d like the embedded >> components to >>>> be able to connect to the broker without a username or password. >>>> >>>> Is there a way to configure ActiveMQ to allow anonymous/guest access for >>>> VM connections only? >>>> >>>> >>>> >>>> >> >>
