tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From YC Lui <y...@us.ibm.com>
Subject Tomcat 5.5 Security Enabled
Date Wed, 15 Aug 2007 16:10:00 GMT
I am a new Tomcat user. 

I installed Tomcat 5.5 for use within IBM RAD/Eclipse runtime environment. 
 My goal is to find out how J2EE container managed (form based) security 
works in Tomcat.

I started off by creating a JSF page, PH001, in the WebContect.  No 
security entry is specified in the web.xml file yet.   I was able to run 
and display the page.

Then I tried to check the Server Security Enable box and restart Tomcat to 
run the same JSF page.  I got the following exception:

        Caused by: java.security.AccessControlException: Access denied 
(java.util.PropertyPermission 
org.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER read)
        at java.security.AccessController.checkPermission(
AccessController.java:104)
        at java.lang.SecurityManager.checkPermission(
SecurityManager.java:547)
        at java.lang.SecurityManager.checkPropertyAccess(
SecurityManager.java:1300)
        at java.lang.System.getProperty(System.java:369)
        at org.apache.jasper.runtime.BodyContentImpl.<clinit>(
BodyContentImpl.java:43)
        at java.lang.J9VMInternals.initializeImpl(Native Method)
        at java.lang.J9VMInternals.initialize(J9VMInternals.java:177)
        ... 64 more 

 
The default catalalina.policy file in the server is appended below :  What 
update do I need in the file to bypass the exception ?   Thank you in 
advance for any help.

 

        // 
============================================================================
// catalina.corepolicy - Security Policy Permissions for Tomcat 5
//
// This file contains a default set of security policies to be enforced 
(by the
// JVM) when Catalina is executed with the "-security" option.  In 
addition
// to the permissions granted here, the following additional permissions 
are
// granted to the codebase specific to each web application:
//
// * Read access to the document root directory
//
// $Id: catalina.policy 393732 2006-04-13 06:32:25Z pero $
// 
============================================================================


// ========== SYSTEM CODE PERMISSIONS 
=========================================


// These permissions apply to javac
grant codeBase "file:${java.home}/lib/-" {
        permission java.security.AllPermission;
};

// These permissions apply to all shared system extensions
grant codeBase "file:${java.home}/jre/lib/ext/-" {
        permission java.security.AllPermission;
};

// These permissions apply to javac when ${java.home] points at 
$JAVA_HOME/jre
grant codeBase "file:${java.home}/../lib/-" {
        permission java.security.AllPermission;
};

// These permissions apply to all shared system extensions when
// ${java.home} points at $JAVA_HOME/jre
grant codeBase "file:${java.home}/lib/ext/-" {
        permission java.security.AllPermission;
};


// ========== CATALINA CODE PERMISSIONS 
=======================================


// These permissions apply to the launcher code
grant codeBase "file:${catalina.home}/bin/commons-launcher.jar" {
        permission java.security.AllPermission;
};

// These permissions apply to the daemon code
grant codeBase "file:${catalina.home}/bin/commons-daemon.jar" {
        permission java.security.AllPermission;
};

// These permissions apply to the commons-logging API
grant codeBase "file:${catalina.home}/bin/commons-logging-api.jar" {
        permission java.security.AllPermission;
};

// These permissions apply to the server startup code
grant codeBase "file:${catalina.home}/bin/bootstrap.jar" {
        permission java.security.AllPermission;
};

// These permissions apply to the JMX server
grant codeBase "file:${catalina.home}/bin/jmx.jar" {
        permission java.security.AllPermission;
};

// These permissions apply to JULI
grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
        permission java.security.AllPermission;
};

// These permissions apply to the servlet API classes
// and those that are shared across all class loaders
// located in the "common" directory
grant codeBase "file:${catalina.home}/common/-" {
        permission java.security.AllPermission;
};

// These permissions apply to the container's core code, plus any 
additional
// libraries installed in the "server" directory
grant codeBase "file:${catalina.home}/server/-" {
        permission java.security.AllPermission;
};

// The permissions granted to the balancer WEB-INF/classes and WEB-INF/lib 
directory
grant codeBase "file:${catalina.home}/webapps/balancer/-" {
        permission java.lang.RuntimePermission 
"accessClassInPackage.org.apache.tomcat.util.digester";
        permission java.lang.RuntimePermission 
"accessClassInPackage.org.apache.tomcat.util.digester.*";
};
// ========== WEB APPLICATION PERMISSIONS 
=====================================


// These permissions are granted by default to all web applications
// In addition, a web application will be given a read FilePermission
// and JndiPermission for all files and directories in its document root.
grant { 
    // Required for JNDI lookup of named JDBC DataSource's and
    // javamail named MimePart DataSource used to send mail
    permission java.util.PropertyPermission "java.home", "read";
    permission java.util.PropertyPermission "java.naming.*", "read";
    permission java.util.PropertyPermission "javax.sql.*", "read";

    // OS Specific properties to allow read access
    permission java.util.PropertyPermission "os.name", "read";
    permission java.util.PropertyPermission "os.version", "read";
    permission java.util.PropertyPermission "os.arch", "read";
    permission java.util.PropertyPermission "file.separator", "read";
    permission java.util.PropertyPermission "path.separator", "read";
    permission java.util.PropertyPermission "line.separator", "read";

    // JVM properties to allow read access
    permission java.util.PropertyPermission "java.version", "read";
    permission java.util.PropertyPermission "java.vendor", "read";
    permission java.util.PropertyPermission "java.vendor.url", "read";
    permission java.util.PropertyPermission "java.class.version", "read";
        permission java.util.PropertyPermission 
"java.specification.version", "read";
        permission java.util.PropertyPermission 
"java.specification.vendor", "read";
        permission java.util.PropertyPermission "java.specification.name", 
"read";

        permission java.util.PropertyPermission 
"java.vm.specification.version", "read";
        permission java.util.PropertyPermission 
"java.vm.specification.vendor", "read";
        permission java.util.PropertyPermission 
"java.vm.specification.name", "read";
        permission java.util.PropertyPermission "java.vm.version", "read";
        permission java.util.PropertyPermission "java.vm.vendor", "read";
        permission java.util.PropertyPermission "java.vm.name", "read";

    // Required for OpenJMX
    permission java.lang.RuntimePermission "getAttribute";

        // Allow read of JAXP compliant XML parser debug
        permission java.util.PropertyPermission "jaxp.debug", "read";

    // Precompiled JSPs need access to this package.
    permission java.lang.RuntimePermission 
"accessClassInPackage.org.apache.jasper.runtime";
    permission java.lang.RuntimePermission 
"accessClassInPackage.org.apache.jasper.runtime.*";
 
};


// You can assign additional permissions to particular web applications by
// adding additional "grant" entries here, based on the code base for that
// application, /WEB-INF/classes/, or /WEB-INF/lib/ jar files.
//
// Different permissions can be granted to JSP pages, classes loaded from
// the /WEB-INF/classes/ directory, all jar files in the /WEB-INF/lib/
// directory, or even to individual jar files in the /WEB-INF/lib/ 
directory.
//
// For instance, assume that the standard "examples" application
// included a JDBC driver that needed to establish a network connection to 
the
// corresponding database and used the scrape taglib to get the weather 
from
// the NOAA web server.  You might create a "grant" entries like this:
//
// The permissions granted to the context root directory apply to JSP 
pages.
// grant codeBase "file:${catalina.home}/webapps/examples/-" {
//      permission java.net.SocketPermission "dbhost.mycompany.com:5432", 
"connect";
//      permission java.net.SocketPermission "*.noaa.gov:80", "connect";
// };
//
// The permissions granted to the context WEB-INF/classes directory
// grant codeBase 
"file:${catalina.home}/webapps/examples/WEB-INF/classes/-" {
// };
//
// The permission granted to your JDBC driver
// grant codeBase 
"jar:file:${catalina.home}/webapps/examples/WEB-INF/lib/driver.jar!/-" {
//      permission java.net.SocketPermission "dbhost.mycompany.com:5432", 
"connect";
// };
// The permission granted to the scrape taglib
// grant codeBase 
"jar:file:${catalina.home}/webapps/examples/WEB-INF/lib/scrape.jar!/-" {
//      permission java.net.SocketPermission "*.noaa.gov:80", "connect";
// };

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message