Summary
RMI is not designed for developing secure distributed programs. RMI offers little by way of client authentication, operation-level authorization, confidentiality, and integrity of messages exchanged. However, there are enough hooks to add security by careful program design and use of other security APIs such as JSSE for message integrity and confidentiality, and JAAS for user authentication and authorization.
RMI offers protection against rogue downloaded code by requiring a security manager. This forces the application deployer to think about limiting the privileges for the downloaded code and assign them appropriate permissions.
SSL can be used to protect the RMI payloads, and optionally authenticate the communicating end-points. RMI ...
Get J2EE™ Security for Servlets, EJBs and Web Services: Applying Theory and Standards to Practice now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
