Security plays an important role in distributed systems. The Jini security model is based on the JDK 1.2 security system.
This will be expanded more in future - now it is just to fix a problem that some people might have
Security for Jini is based on the JDK 1.2 security model.
This makes use of a SecurityManager
to grant
or deny access to resources.
Some of the examples may work fine without a security manager
(depending on your system. Or your luck???). Others may
require an appropriate security manager in place.
Installing a suitable manager may be done by
System.setSecurityManager(new RMISecurityManager());
This should be done before any network-related calls.
The security manager will need to make use of a
security policy. This is typically
done in policy files which are in default locations or
are specified to the Java runtime. If policy.all
is a policy file in the current directory, then invoking the
runtime by
java -Djava.security.policy="policy.all" ...
will load the contents of the policy file.
A totally permissive policy file can contain
grant {
permission java.security.AllPermission "", "";
};
This will allow all permissions, and should not be used
outside of a test and development environment.
This file is Copyright ©Jan Newmarch
(http://jan.newmarch.name)
jan@newmarch.name