RE: RE: [Mx4j-user] RE: mx4j-Bugs-969175: Security and delegation

All,

Other comments, which are not at all critical to us, but are worth some
consideration are the following:

We know that when a client connects to an Mserver, a subject is
eventually created and associated with the running thread, so if some
Mbean is invoked, the subject's permissions are considered.
The RMI implementation and spec provide means for the client to specify
who he is by supplying credentials, but provide no means for the client
to identify the server.

However, if this client registers for some notification and later
notified, on the client there is no information what so ever about which
entity initiated the notification and thus the client side code
associated with the listener is executed (probably) with the connector's
permission. In practice, the "server" may possibly be running with
several different associated subjects. In current implementation, the
client does not know of any (not even one) and thus is likely running
with the wrong set of permissions when a notification is received.

Last, I think it should be made easier to plug-in different
authentication models.
Currently, while I like the Kerberos based idea, I think its not really
an option and is more difficult to deploy (leave it in though!).

If we look at RMI, than we get JMXAuthenticator, which allows for
client-only authentication with a single unidirectional message (not
good enough).
Of course I can write my own connector server, but if the spec will
either allow more options (e.g. real challenge-response) AND allow to
plugin your own thereby allowing client AND server authentication,
possibly arbitrary number of messages for authentication stage, that
would be great.

I leave it up to you to raise possible solutions.

Thank you,
Ron.

------------------------------------------------------------------------------
This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Siebel Systems, Inc. or its customers or partners.  Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited.  If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments.  Thank you for your cooperation.
====================================================



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idP47&alloc_id808&op=click