[
https://jira.jboss.org/browse/JBAS-8159?page=com.atlassian.jira.plugin.sy...
]
Xavier MOGHRABI edited comment on JBAS-8159 at 8/2/10 4:30 AM:
---------------------------------------------------------------
Hi,
I've also noticed that some MBeans throw UnmarchalException. The RMIAdaptor includes a
interceptor that prevent the rise of this exception.
So I've integrated a similar behaviour to the JSR 160 connector.
Please find the source in attachement.
was (Author: moghrabi):
Hi,
I've also noticed that some MBeans throw UnmarchalException. The RMIAdaptor includes a
interceptor that prevent the rise of this exception.
So I've integrated a similar behaviour to the JSR 160 connector.
Pleas find the source in attached.
Secure jmx-remoting.sar
-----------------------
Key: JBAS-8159
URL:
https://jira.jboss.org/browse/JBAS-8159
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMX
Affects Versions: JBossAS-5.1.0.GA
Environment: JBossAS 5.1.0 GA
Reporter: Xavier MOGHRABI
Assignee: Scott Marlow
Fix For: 7.0.0.M1
Attachments: jboss-service.xml, jbossas-jmx-remoting-src.jar,
jmx-remoting-src.zip
JBossAS 5.1.0 GA provides jmx-remoting.sar compliant to JSR 160. Unfortunately the
service is not secured and doesn't provide any way to secure it.
However the JMX API provides several mechanisms allowing authentication and
authorization. Authentication can easily done against a login-module.
A forwarder can be implemented to extend the authorization against a role based
mechanism.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira