Good point. Since Marco is proposing using an applet, a simple solution would be to use the webserver security configuration to protect access to the page containing the applet.
The JMX Remote API spec, JSR 160 does include security features and MX4J does include a section on using a JMXAuthenticator. I don't know if it is easy to use this via Phoenix but I can take a closer look if we agree on a JMX based approach. Steve > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > Sent: Monday, December 08, 2003 10:22 AM > To: James Users List > Subject: RE: Connecting to james from outside > > > > I'd suggest that we go JMX now since most JMX > implementations have an > > RMI adaptor, including MX4J. It is a straightforward > process to Add > > the Mbean and Xdoclet tags (or .mxinfo file) to expose the major > > components as Mbeans. I can do this and submit a patch today / > > tomorrow if you like. This would not give immediate access > to all of > > the management functions required but if would be a good starting > > point. > > Works for me. But we cannot expose JMX without security. > That was a problem in an earlier release. > > --- Noel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
