java.lang.Objectjava.security.Policy
Direct Known Subclasses:
PolicyDelegate
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".
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.
Roland
- SchemersGary
- EllisonNested Class Summary: | ||
---|---|---|
public static interface | Policy.Parameters | This represents a marker interface for Policy parameters. |
Field Summary | ||
---|---|---|
public static final PermissionCollection | UNSUPPORTED_EMPTY_COLLECTION | A read-only empty PermissionCollection instance.
|
Method from java.security.Policy Summary: |
---|
getInstance, getInstance, getInstance, getParameters, getPermissions, getPermissions, getPolicy, getPolicyNoCheck, getProvider, getType, implies, isSet, refresh, setPolicy |
Methods from java.lang.Object: |
---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Method from java.security.Policy Detail: |
---|
This method traverses the list of registered security providers, starting with the most preferred Provider. A new Policy object encapsulating the PolicySpi implementation from the first Provider that supports the specified type is returned. Note that the list of registered providers may be retrieved via the Security.getProviders() method. |
A new Policy object encapsulating the PolicySpi implementation from the specified provider is returned. The specified provider must be registered in the provider list. Note that the list of registered providers may be retrieved via the Security.getProviders() method. |
A new Policy object encapsulating the PolicySpi implementation from the specified Provider object is returned. Note that the specified Provider object does not have to be registered in the provider list. |
This Policy instance will only have parameters if it
was obtained via a call to |
Applications are discouraged from calling this method
since this operation may not be supported by all policy implementations.
Applications should solely rely on the The default implementation of this method returns Policy.UNSUPPORTED_EMPTY_COLLECTION. This method can be overridden if the policy implementation can return a set of permissions granted to a CodeSource. |
Applications are discouraged from calling this method
since this operation may not be supported by all policy implementations.
Applications should rely on the The default implementation of this method first retrieves
the permissions returned via This method can be overridden if the policy implementation supports returning a set of permissions granted to a ProtectionDomain. |
setPolicy .
This method first calls
SecurityManager.checkPermission with a
SecurityPermission("getPolicy") permission
to ensure it's ok to get the Policy object. |
|
This Policy instance will only have a Provider if it
was obtained via a call to |
This Policy instance will only have a type if it
was obtained via a call to |
|
|
refresh
on a file-based policy will cause the file to be re-read.
The default implementation of this method does nothing. This method should be overridden if a refresh operation is supported by the policy implementation. |
SecurityManager.checkPermission with a
SecurityPermission("setPolicy")
permission to ensure it's ok to set the Policy. |