Permission classes are used to define what Permissions a class loaded by Tomcat will have. There are a number of Permission classes that are a standard part of the JDK, and you can create your own Permission class for use in your own web applications. Both techniques are used in Tomcat.<\/p>\n
Standard Permissions<\/strong><\/span><\/p>\n This is just a short summary of the standard system SecurityManager Permission classes applicable to Tomcat.<\/p>\n java.util.PropertyPermission<\/strong> – Controls read\/write access to JVM properties such as java.home.<\/p>\n java.lang.RuntimePermission –<\/strong> Controls use of some System\/Runtime functions like exit() and exec(). Also control the package access\/definition.<\/p>\n java.io.FilePermission –<\/strong> Controls read\/write\/execute access to files and directories.<\/p>\n java.net.SocketPermission –<\/strong> Controls use of network sockets.<\/p>\n java.net.NetPermission –<\/strong> Controls use of multicast network connections.<\/p>\n java.lang.reflect.ReflectPermission – <\/strong>Controls use of reflection to do class introspection.<\/p>\n java.security.SecurityPermission –<\/strong> Controls access to Security methods.<\/p>\n java.security.AllPermission –<\/strong> Allows access to all permissions, just as if you were running Tomcat without a SecurityManager.<\/p>\n Tomcat Custom Permissions<\/strong><\/span><\/p>\n Tomcat utilizes a custom permission class called org.apache.naming.JndiPermission. This permission controls read access to JNDI named file based resources. The permission name is the JNDI name and there are no actions. A trailing “*” can be used to do wild card matching for a JNDI named file resource when granting permission. For example, you might include the following in your policy file:<\/p>\n permission org.apache.naming.JndiPermission “jndi:\/\/localhost\/examples\/*”;<\/p>\n A Permission entry like this is generated dynamically for each web application that is deployed, to allow it to read its own static resources but disallow it from using file access to read any other files (unless permissions for those files are explicitly granted).<\/p>\n Also, Tomcat always dynamically creates the following file permissions:<\/p>\n permission java.io.FilePermission “** your application context**”, “read”;<\/p>\n <\/p>\n permission java.io.FilePermission<\/p>\n “** application working directory**”, “read,write”;<\/p>\n permission java.io.FilePermission<\/p>\n “** application working directory**\/-“, “read,write,delete”;<\/p>\n Where **your application context** equals the folder (or WAR file) under which your application has been deployed and **application working directory** is the temporary directory provided to your application as required by the Servlet Specification.<\/p>\n","protected":false},"excerpt":{"rendered":" Permission classes are used to define what Permissions a class loaded by Tomcat will have. There are a number of Permission classes that are a standard part of the JDK, and you can create your own Permission class for use in your own web applications. Both techniques are used in Tomcat. Standard Permissions This is…<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"categories":[8678],"tags":[2642],"class_list":["post-75535","page","type-page","status-publish","hentry","category-tomcat","tag-permissions"],"acf":[],"yoast_head":"\n