-
1. Re: Wildfly AccessControlException setting security policy
lsgroup Jun 24, 2014 6:39 PM (in response to lsgroup)I forgot to mention that I am running jdk 8. I noticed that JDK 8 uses a new method of security - jar file manifest attributes. Are these permissions attributes applicable to an ear deployed inside Wildfly?
-
2. Re: Wildfly AccessControlException setting security policy
lsgroup Jun 24, 2014 10:42 PM (in response to lsgroup)Adding a MANIFEST.MF with text:
Permissions: all-permissions
did not change the situation. However, I found this post:
I applied the following changes to standalone-full.xml
<extension module="org.wildfly.extension.security.manager" />
...
<subsystem xmlns="urn:jboss:domain:security-manager:1.0">
<deployment-permissions>
<minimum-set>
<permission class="java.io.FilePermission" name="/tmp" actions="read,write"/>
<permission class="java.io.FilePermission" name="/opt" actions="read"/>
<permission class="java.lang.RuntimePermission" name="createClassLoader"/>
<permission class="java.util.logging.LoggingPermission" name="control"/>
<permission class="java.security.AllPermission"/>
</minimum-set>
<maximum-set>
<permission class="java.security.AllPermission"/>
</maximum-set>
</deployment-permissions>
</subsystem>
And got past the initial error. However, when running my application, I get ...
19:30:32,724 ERROR [stderr] (default task-1) java.lang.SecurityException: WFSM000002: Security manager may not be changed
-
3. Re: Wildfly AccessControlException setting security policy
lsgroup Jun 27, 2014 12:39 PM (in response to lsgroup)The last error about Security manager may not be changed has to do with some specific code I have which might be better posted as a separate post.