Hi!
Andy \"Mad\" Schaefer wrote:
> Yeah, JMX is dumb security wise but is Weblogic or WebSphere better
> with their console. If you now their protocol you can still access a App.
> Server and change them without the right access rights (or am I wrong).
>
> >From my point of view to add security is not simple but straight forward
> when we can create our own JMX MBeanServer:
> - add a Security Service like the <MLET> service which is available
> from the startup of MBeanServer.
> - before executing a method (get, set, invoke, add or remote Notification
> listener the MBeanServer asks the Security Service if the user has the
> right permission.
> - the Security Service can then check its DB and see if the user is allowed
> to do what he/she wants to do
> - if the Security Service does not give permission it throws an Exception
>
> Do you like it?
Security and JMX is being discussed by the JMX board, and we should
probably not do anything too soon (or else risk having to redo it once
they complete). A simple solution is to just let the RMI adaptor
authenticate the client on connect. I have some code (basicallt an RMI
socket factory) that can be adapted to this purpose.
regards,
Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
