I added a reference to securityHandler as you mentioned but again the result is same as it did not ask for login after restarting the broker.
cobrien wrote: > > I think you are missing a reference to the security handling in your list > of handlers. > > > Should be something like: > > <property name="handlers"> > <list> > <ref bean="securityHandler" /> > <bean.... > > > > > Clark > > > www.ttmsolutions.com > ActiveMQ reference guide at > http://bit.ly/AMQRefGuide > > > > > > vbose wrote: >> >> I tried to follow the steps mentioned at the URL >> http://www.nighttale.net/activemq/securing-activemq-531-console.html >> securing-activemq-531-console to secure ActiveMQ 5.3.2 web console. But >> it did not work for me. >> >> I have installed activeMQ 5.3.2 under /opt/ in our Test Linux servers. >> Then I configured the embedded jetty.xml as per your recommendation. The >> file is located in /opt/apache-activemq-5.3.2/conf. Then I restarted >> activeMQ broker. But the activeMQ browser app running on port 8161 did >> not ask for login. I have a property file called amqrealm.properties >> located in /opt/apache-activemq-5.3.2/conf. The jetty.xml configuration >> is uploaded for reference. >> >> I am using activemq script from the folder >> /opt/apache-activemq-5.3.2/bin/linux-x86-32 to start the broker. Did I >> miss anything? >> >> >> http://old.nabble.com/file/p28892934/activeMQ-jetty.txt >> activeMQ-jetty.txt >> >> >> > > -- View this message in context: http://old.nabble.com/Securing-ActiveMQ-5.3.2-Web-console-tp28892934p28894164.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.