There is only one Policy object installed in the runtime at any given time. A Policy object can be installed by calling the setPolicy
method. The installed Policy object can be obtained by calling the getPolicy
method.
If no Policy object has been installed in the runtime, a call to getPolicy
installs an instance of the default Policy implementation (a default subclass implementation of this abstract class). The default Policy implementation can be changed by setting the value of the "policy.provider" security property (in the Java security properties file) to the fully qualified name of the desired Policy subclass implementation. The Java security properties file is located in the file named <JAVA_HOME>/lib/security/java.security. <JAVA_HOME> refers to the value of the java.home system property, and specifies the directory where the JRE is installed.
Application code can directly subclass Policy to provide a custom implementation. In addition, an instance of a Policy object can be constructed by invoking one of the getInstance
factory methods with a standard type. The default policy type is "JavaPolicy". See Appendix A in the Java Cryptography Architecture API Specification & Reference for a list of standard Policy types.
Once a Policy instance has been installed (either by default, or by calling setPolicy
), the Java runtime invokes its implies
when it needs to determine whether executing code (encapsulated in a ProtectionDomain) can perform SecurityManager-protected operations. How a Policy object retrieves its policy data is up to the Policy implementation itself. The policy data may be stored, for example, in a flat ASCII file, in a serialized binary file of the Policy class, or in a database.
The refresh
method causes the policy object to refresh/reload its data. This operation is implementation-dependent. For example, if the policy object stores its data in configuration files, calling refresh
will cause it to re-read the configuration policy files. If a refresh operation is not supported, this method does nothing. Note that refreshed policy may not have an effect on classes in a particular ProtectionDomain. This is dependent on the Policy provider's implementation of the implies
method and its PermissionCollection caching strategy.
@author Roland Schemers
@author Gary Ellison
@version 1.103, 11/17/06
@see java.security.Provider
@see java.security.ProtectionDomain
@see java.security.Permission
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|