[jboss-jira] [JBoss JIRA] (WFLY-400) Deployment descriptor parsing of META-INF/permissions.xml

[Shane Kingston (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967720#comment-12967720 ] 

Shane Kingston commented on WFLY-400:
-------------------------------------

Hi, is there an example or test case for a deployment with a permissions.xml or jboss-permission.xml? I have tried including one with a deployment in both 8.0-final and 8.1CR2 without any effect, but I may be doing the wrong thing. Even a badly formatted XML file is ignored.

I have an application which uses an old version of Mule that requires permissions to access to "findMBeanServer" on javax.management.MBeanServerPermission, as well as other things. We previously had a policy file that granted the 'java.security.AllPermission' permission that worked around this. The policy file was set using the "-Djava.security.policy" argument to the Jboss startup script.

The application structure is an ear containing a war (as well as other things). Inside the war's META-INF folder I added a permissions.xml.

Is someone able to help me figure out how to do this with Jboss 8? Or provide an example deployment containing one of these files which is known to work.

> Deployment descriptor parsing of META-INF/permissions.xml
> ---------------------------------------------------------
>
>                 Key: WFLY-400
>                 URL: https://issues.jboss.org/browse/WFLY-400
>             Project: WildFly
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Security Manager
>            Reporter: Anil Saldhana
>            Assignee: Stefan Guilhen
>             Fix For: 8.0.0.Alpha4
>
>
> EE 6.2.2.6 Permission declarations must be stored in META-INF/permissions.xml file
> within an EJB, web, or application client archive in order for them to be located
> and subsequently processed by the deployment machinery of the Java EE Product.
> The permissions for a library are the same as the permissions for the code that
> EE.6.2.2.6.2  Permission Declaration Example
> <?xml version="1.0" encoding="UTF-8"?>
> <permissions>
> <permission>
> <classname>java.io.FilePermission</classname>
> <name>/tmp/abc</name>
> <actions>read,write</actions>
> </permission>
> <permission>
> <classname>java.lang.RuntimePermission</classname>
> <name>createClassLoader</name>
> </permission>
> </permissions>
> The EE7 spec draft has a schema for permissions.xml



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)