Hi, it all depends on your environment and use case.
If you have a small number of clients that you control, you can easily go with user/pass version (and using ssl just to encrypt data). If you expect large number of clients and you might to think about LDAP so that you can manage user credentials more easily. So there's no right or wrong way, it's just what you need (and keep it as simple as possible :) Regards -- Dejan Bosanac ---------------------- Red Hat, Inc. FuseSource is now part of Red Hat dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Thu, Nov 29, 2012 at 2:38 PM, joesan <codeintheo...@gmail.com> wrote: > Thanks for the reply. I can see from the ActiveMQ documentation that there > are many possible ways to do Authentication and Authorization. For example., > to Authenticate, I can use SSL, JAAS Certificate Authentication, JAAS LDAP > Authentication, JAAS Username, Password Authentication. > > What would you advice to use? I have an SSL connection on my ActiveMQ > instance with my clients. I have also implemented JAAS Certificate > Authentication. Is this a better approach or is JAAS LDAP Authentication and > Authorization the way to go? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-Authorization-Performace-tp4659927p4659938.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
