[
http://jira.jboss.com/jira/browse/JBAS-4167?page=comments#action_12357866 ]
Johnny Walker commented on JBAS-4167:
-------------------------------------
Binding to localhost is great - except that I'm running more than 1 instance on the
same server in a 64 bit windows environment.
Setting up weak basic auth means I have to edit at least 4 files per jmx, web-console on
each instance, so for this project that's 5 instances across 3 servers - 20 or more
files just for BASIC auth ??
Wouldn't a gui to create key based auth be nice?
I suppose I'll go the quick route and setup LDAP... (more work than I was looking
for)
JMX Console not secured by default
----------------------------------
Key: JBAS-4167
URL:
http://jira.jboss.com/jira/browse/JBAS-4167
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Ryan Campbell
Assigned To: Dimitris Andreadis
The jmx and web consoles should be inaccessible to remote hosts by default upon
installation. However, I just installed the alpha build and was able to access the jmx
console remotely. Steps to reproduce
./run.sh -b $MYTESTIP
Everything starts up correctly. However, I can access $MYTESTIP:8080/jmx-console from my
browser without restriction
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira