[jboss-jira] [JBoss JIRA] Updated: (JBAS-4154) Get the server to run under a security manager

[Jason T. Greene (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason T. Greene updated JBAS-4154:
----------------------------------

    Fix Version/s: JBossAS-5.1.0.GA
                       (was: JBossAS-5.1.0.CR1)


> Get the server to run under a security manager
> ----------------------------------------------
>
>                 Key: JBAS-4154
>                 URL: https://jira.jboss.org/jira/browse/JBAS-4154
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Security
>    Affects Versions: JBossAS-5.0.0.Beta1
>            Reporter: Scott M Stark
>            Assignee: Anil Saldhana
>            Priority: Critical
>             Fix For: JBossAS-5.1.0.GA
>
>
> The testsuite tests-security-manager target was failing due to the aop layer not creating classes with correct ProtectionDomains. This is fixed in (JBAOP-368). The next problem is that the server.policy needs to use vfsfile urls for the permission assignments. However, because these are URLs and not URIs, there has to be a URL handler available when the policy is read at bootstrap. Currently a policy entry like:
> grant codeBase "vfsfile:${jboss.home.dir}/lib/-" {
>    permission java.security.AllPermission;
> };
> fails because the jboss vfsfile URL handler is unknown:
> policy: Adding policy entry:
> policy:   signedBy null
> policy:   codeBase vfsfile:/tmp/trunk/build/output/jboss-5.0.0.Beta2/lib/-
> java.security.policy: error adding Entry:
>         java.net.MalformedURLException: unknown protocol: vfsfile policy:

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira