2 Replies Latest reply on Dec 4, 2007 12:47 PM by adrian.brock

Security errors with maven tests

pgier Dec 4, 2007 12:21 PM

I'm working on completing the maven migration for aop and I'm getting some errors when running the unit tests. I thought I would ask here before spending too much time trying to figure it out.

Testcase: testSubSuperOnlyMetadata took 0.458 sec
Testcase: testSubSubSuperOnlyMetadata took 0.008 sec
 Caused an ERROR
null
java.lang.reflect.InvocationTargetException
 at org.jboss.test.AbstractTestDelegate.getDelegate(AbstractTestDelegate.java:73)
 at org.jboss.test.AbstractTestSetup.setUp(AbstractTestSetup.java:62)
 at org.jboss.test.AbstractTestCaseWithSetup.setUp(AbstractTestCaseWithSetup.java:103)
Caused by: java.security.AccessControlException: access denied (java.util.PropertyPermission * read,write)
 at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
 at java.security.AccessController.checkPermission(AccessController.java:427)
 at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
 at java.lang.SecurityManager.checkPropertiesAccess(SecurityManager.java:1252)
 at java.lang.System.getProperties(System.java:561)
 at org.jboss.test.aop.AOPTestDelegate$1.run(AOPTestDelegate.java:51)
 at org.jboss.test.aop.AOPTestDelegate$1.run(AOPTestDelegate.java:49)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.jboss.test.aop.AOPTestDelegate.<init>(AOPTestDelegate.java:47)
 at org.jboss.test.aop.AOPTestWithSetup.getDelegate(AOPTestWithSetup.java:53)
 ... 19 more

Any ideas why I'm getting these security errors running the tests with maven but not with ant?

1. Re: Security errors with maven tests

anil.saldhana Dec 4, 2007 12:35 PM (in response to pgier)

It is possible that the Java Security Manager is enabled and you will need to add appropriate Java permissions.
Actions
2. Re: Security errors with maven tests

adrian.brock Dec 4, 2007 12:47 PM (in response to pgier)
This is the security policy from jboss-test.
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/projects/test/trunk/src/main/java/org/jboss/test/security/TestsPolicyPlugin.java?revision=62656&view=markup

Specifically:
// Is this a test location? File file = new File(url.toString()); String name = file.getName(); if (name.indexOf("tests") != -1 || name.indexOf("test-classes") != -1 || name.indexOf("-test.jar") != -1) {

Your AOPTestDelegate class will be in target/test-classes so it gets no permissions.
If you can't figure out how to do it properly, you can workaround the problem with a hack.

You can't suspend the security manager, but there is somebody who can. ;-)

import org.jboss.test.AbstractTestCaseWithSetup; // turn off security SecurityManager sm = AbstractTestCaseWithSetup.suspendSecurity(); try { // do bad things here } finally { // resume security AbstractTestCaseWithSetup.resumeSecurity(sm); }

This is only intended for test infrastructure.
The point of testing with a security manager enabled is to determine which parts
of the code need privileged blocks to work correctly.
Actions

Go to original post