blob: e254942d25121e897ddbcd5714de61556b6bf6f0 [file] [log] [blame]
// $Id: jspwiki-container.policy,v 1.1 2007-05-29 05:11:59 arj Exp $
// If you are running your servlet container with a security
// policy already, you should simply append the contents
// of this block into your global JVM policy. The following block
// is designed for inclusion in typical Tomcat security policy
// (for example: $CATALINA_HOME/conf/catalina.policy).
// If you need to include JSPWiki permissions (e.g., PagePermission) in your
// global policy (not shown in the block below), you MUST ALSO:
// 1) sign the JSPWiki.jar file. We provide a sample Ant target that
// does this called 'signjar' (see the build.xml file).
// 2) Copy the keystore used to sign the JAR to the same directory
// as the container security policy (e.g., from JSPWiki's etc/jspwiki.jks
// to $CATALINA_HOME/conf)
// 3) Specify the name of the keystore in your container policy. That's
// this next line (which we have commented out):
// keystore "jspwiki.jks";
// If you don't want or need to specify JSPWiki permissions in your global
// security policy, then don't worry about the preceding paragraphs, jar-signing
// or the keystore line... and just copy the rest of this file into the policy.
// You will also want to adjust the 'codeBase' location to reflect your actual
// JSPWiki.jar location. But don't change the permissions themselves, because
// that will totally b0rk the system.
grant codeBase ""file:${catalina.home}/webapps/JSPWiki/JSPWiki.jar" {
permission "getPolicy";
permission "setPolicy";
permission java.util.PropertyPermission "", "write";
permission java.util.PropertyPermission "", "read,write";
permission "getLoginConfiguration";
permission "setLoginConfiguration";