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

Here's how we could consider changing the API.  Suppose a security 
context (subject and/or codebase and/or signers), say "creator", makes a

JMXConnectorServer and supplies a JMXAuthenticator.  Later, a connection

arrives, and the JMXAuthenticator returns a Subject for it containing 
the Principal "remote".  Today, basically both "remote" and "creator" 
must have all needed permissions for the reason I detailed.  However, 
suppose we say that an MBean operation that needs FilePermission is 
allowed if EITHER:
(1) both "remote" and "creator" have FilePermission (the current 
requirement); OR
(2) "remote" has FilePermission and "creator" has 
SubjectDelegationPermission("remote").

[Ron] This is OK provided the "remote" is some specified principal class
and name, both of the policy writer's choosing and where it can
potentially be "*" for all.

Concerning your second request, to be able to have several authenticated

Subjects use the same RMI connection without using delegation, I am not 
convinced that this gets you enough, compared with simply opening a 
connection per authenticated Subject, to justify the additional 
complexity.  RMI can share the actual network connections between a pair

of JVMs anyway -- it doesn't have to open a different TCP/IP connection 
for each RMI connection, except in circumstances (involving socket 
factories) where it would be impossible to share the JMX Remote 
connection anyway.
[Ron] I don't understand what complexity you are referring to, in
addition to passing in Subject argument, have an overload accepting
credentials, similar to a connect. Basically, make delegation and
connection symmetric.
Note that RMI may be able to do this multiplexing in some scenarios, but
please also consider load-balanced applications and other transports.
You already (wisely) decided to have delegation, so please support it in
a symmetric manner, which allows different security models to be
implemented.

------------------------------------------------------------------------------
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