Christopher- JAAS is a Java standard for performing authentication and authorization for Java server-side processes.
To prevent auto-creation, you at least need authorization. You can still use an authentication-less design, by enabling anonymous accounts to be mapped to an anonymous-group. You the set an authorization policy with read=“anonymous-group” write=“anonymous-group” and do not include “anonymous-group” in the ‘admin’ privilege which is what enables auto-creation of destinations. -Matt > On Jul 25, 2022, at 5:31 PM, Christopher Pisz <[email protected]> > wrote: > > I am trying to stop the auto creation of queues. A quick Google takes me to > this page: > https://activemq.apache.org/how-do-i-restrict-connections-from-creating-new-queues-or-topics > > Which takes me to a page that talks about authentication plugins. > > It starts by talking about JAAS, which completely loses me. I am not using > Java and my client is a custom written stomp over websockets client that > connects to my ActiveMQ instance. > > Currently, I have no authentication set up, and probably don't have a need > for it, as the whole thing is on an internal network anyway. > > My question then is, do I still need authentication to stop auto creation > of queues? If so, how do I even authenticate from the client side when I am > programming a c++ app?
