activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j0llyr0g3r <>
Subject Securing the web console impossible?
Date Fri, 18 Apr 2008 21:22:40 GMT

Hey folks,

i am desperately trying to find out how to configure a simple access control
for the web console, but this is simply not documented......

The documentation here:
refers to a separate jetty instance, not to the integrated jetty.

That's when i thought

 "ok, it's simply not possible using the integrated jetty"

but then i stumbled over this peace of user-submitted configuration example:

This looks really good:

 <!-- Web Console.  Auth is via JAAS.  Beware: jetty-plus-6.1.4.jar contains
       JAAS classes, and is not included with ActiveMQ.  You need to
       separately.  Web Console queue browser will fail, as it tries to use
       to browse the queue, and that requires a password.

  <jetty xmlns="">
      <nioConnector port="8161" />

      <!-- "name" must match the realm in web.xml, and "loginModuleName"
must be defined in login.conf -->
      <jaasUserRealm name="ActiveMQ" loginModuleName="ActiveMQ"

      <webAppContext contextPath="/admin"
resourceBase="${activemq.base}/webapps/admin" logUrlOnStart="true" />

But unfortunately, it lacks important information:

      <!-- "name" must match the realm in web.xml, and "loginModuleName"
must be defined in login.conf -->

Defining a realm in the web.xml is ok, but what about the "login.conf"?

Where should i place this file?

What should its content look like?

What "loginModuleName" should i specify?
View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message