[jboss-jira] [JBoss JIRA] Resolved: (JBAS-7871) Create a JMXAuthenticator implementation which uses our authentication stuff
[
https://jira.jboss.org/jira/browse/JBAS-7871?page=com.atlassian.jira.plug...
]
Scott Marlow resolved JBAS-7871.
--------------------------------
Resolution: Done
tested shutdown, twiddle, jconsole against a secured jmxconnector.
Steps to enable jmxconnector security:
1. Open deploy/jmx-jboss-beans.xml in an editor
2. Replace:
<!-- To enable authentication security checks, uncomment the following security
domain name -->
<!--UNCOMMENT THIS
<property name="securityDomain">jmx-console</property>
-->
With:
<!-- To enable authentication security checks, uncomment the following security
domain name -->
<property name="securityDomain">jmx-console</property>
The jmx-console security will be used (as specified in conf/login-config.xml)
Create a JMXAuthenticator implementation which uses our
authentication stuff
----------------------------------------------------------------------------
Key: JBAS-7871
URL: https://jira.jboss.org/jira/browse/JBAS-7871
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: JMX
Reporter: David Lloyd
Assignee: Scott Marlow
Fix For: JBossAS-6.0.0.M4
Attachments: anil_change.tar, jmxsecure.patch
jconsole instructions for accessing a secured AS:
1. Start AS with jmc connector security enabled.
2. Start jconsole (with adding any options).
3. In the jconsole gui, choose remote option button and enter remote url
"service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi"
4. enter the userid and password and press connect.
Also verify that a bad userid/pw fails the challenge.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira