Name
RMISecurityManager
Synopsis
The RMISecurityManager
enforces the security policy for classes that
are loaded as stubs for remote objects, by overriding all of the
relevant access-check methods from the SecurityManager
. By default,
stub objects are only allowed to perform class definition and class
access operations. If you don’t set the local security manager to be
an RMISecurityManager
(using the System.setSecurityManager()
method),
then stub classes will only be loadable from the local file
system. Applets engaging in RMI calls do not need to use the
RMISecurityManager
, since the security manager provided by the browser
will do the necessary access control on loading remote classes, etc.
You normally won’t need to interact with the RMISecurityManager
directly within your application code, except to set it as the system
security manager before starting your RMI code.
public class RMISecurityManager extends SecurityManager { // Public Constructors public RMISecurityManager(); }
Get Java Enterprise in a Nutshell, Second Edition 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.