activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Norman Maurer (JIRA)" <>
Subject [jira] Commented: (AMQ-3044) Enable securing created JMX connector
Date Thu, 18 Nov 2010 13:47:26 GMT


Norman Maurer commented on AMQ-3044:

Just as a note... secured jmx will not start if the files don't have the proper perms / ownership.
On linux you can do it during packaging, but on windows the user need to set it manual which
is kind of a pain. So if you really want to use auth/pass you should disable it by default
so the user will at least have no problems at the first place.

Related to the security aspect we (JAMES) wrote a custom RMISocketFactory which allows to
bind to a specific ipaddress . Maybe its useful for you too:

> Enable securing created JMX connector
> -------------------------------------
>                 Key: AMQ-3044
>                 URL:
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 5.4.1
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.5.0
> When creating JMX connector (instead using platform one), we should be able to secure
the access with username and password like:
> {code}
>     <managementContext>
>       <managementContext createConnector="true" connectorPort="2011" jmxDomainName="test.domain">
>           <property xmlns="" name="environment">
>               <map xmlns="">
> 				<entry xmlns="" key="jmx.remote.x.password.file"
> 				<entry xmlns="" key="jmx.remote.x.access.file"
>               </map>
>           </property>
>       </managementContext>
>     </managementContext>
> {code}

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message