The need was to secure the jmx-console. I followed the procedure described in
the documentation (Getting Started Guide and the Wiki Knowledge base) but kept
getting a HTTP 403 error when I tried to access the console.
The problem went away only when I added the optional <login-config>
elements to the web.xml file in
JBOSS-HOME/server/all/deploy/jmx-console.war/WEB-INF.
<login-config>
<auth-method>BASIC</auth-method>
</login-config>
Perhaps I did something wrong as the login-config is normally supposed to be
optional. However after doing quite a bit of triaging I couldnt find anything
wrong in the way I configured the server: hence this post.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919661#3919661
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919661
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
