3 Replies Latest reply on May 1, 2019 3:12 PM by jewellgm

    Permission error in WF-16

    goodidea

      190419 12:53:37 ERROR [stderr.write(71)] java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.util.logging.LoggingPermission" "control")" in code source "(vfs:/content/code.ear/core.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.code.ear.core.jar" from Service Module Loader")

       

      Any idea how to fix?

       

       

      Any attention from developers?

       

       

      It is working if I have this:

      <permission class="java.util.logging.LoggingPermission" name="control"/>

      <permission class="java.security.AllPermission"/><!--temporary solution to avoid error-->

       

      Not working:

      <permission class="java.util.logging.LoggingPermission" name="control"/>

       

      It used to work in WF10

        • 1. Re: Permission error in WF-16
          jewellgm

          Is the xml snippet you provided embedded in the permission.xml file in the META-INF directory of your ear?  If so, the entries don't adhere to the schema for Java EE 7.  It should be:

           

          <permission>

              <class-name>java.util.logging.LoggingPermission</class-name>

              <name>control</name>

          </permission>

           

          This doesn't explain why adding the AllPermission permission works though, since that also doesn't conform to the EE 7 schema.

           

          Chapter 5. Java Security Manager - Red Hat Customer Portal

          • 2. Re: Permission error in WF-16
            goodidea

            jewellgm  No. It was part of standalone.xml====>

            <subsystem xmlns="urn:jboss:domain:security-manager:1.0">

               <deployment-permissions>

               <minimum-set>

                 .....

            Do you recommend to set it in META-INF as well or instead? It used to work in standalone.xml though in previous version.

            • 3. Re: Permission error in WF-16
              jewellgm

              My personal recommendation is to use the mechanism dictated by the specification.  In other words, use the permissions.xml file in your ear rather than using the proprietary functionality of the specific application server.  I think it makes things easier to maintain in the long run, and will help prevent issues where proprietary behaviors/functionality change or are removed entirely.