IBM Support

PI73266: AccessControlException issued even when permission was granted in the permissions.xml file

Fixes are available

17.0.0.1: WebSphere Application Server Liberty 17.0.0.1
17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12
21.0.0.3: WebSphere Application Server Liberty 21.0.0.3
21.0.0.4: WebSphere Application Server Liberty 21.0.0.4
21.0.0.5: WebSphere Application Server Liberty 21.0.0.5
21.0.0.6: WebSphere Application Server Liberty 21.0.0.6
21.0.0.7: WebSphere Application Server Liberty 21.0.0.7
21.0.0.8: WebSphere Application Server Liberty 21.0.0.8
21.0.0.9: WebSphere Application Server Liberty 21.0.0.9
21.0.0.1: WebSphere Application Server Liberty 21.0.0.1
21.0.0.2: WebSphere Application Server Liberty 21.0.0.2
21.0.0.10: WebSphere Application Server Liberty 21.0.0.10
21.0.0.11: WebSphere Application Server Liberty 21.0.0.11
21.0.0.12: WebSphere Application Server Liberty 21.0.0.12
22.0.0.1: WebSphere Application Server Liberty 22.0.0.1
22.0.0.2: WebSphere Application Server Liberty 22.0.0.2
22.0.0.3: WebSphere Application Server Liberty 22.0.0.3
22.0.0.4: WebSphere Application Server Liberty 22.0.0.4

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • For WebSphere Application Server Liberty, in some instances
    there is an AccessControlException issued for a permission
    that had been granted in the application's permissions.xml
    file.  For example, for the following
    AccessControlException,
    
    java.security.AccessControlException: Access denied
    ("javax.security.auth.AuthPermission"
    "wssecurity.getRunAsSubject")
    	at
    java.security.AccessController.throwACE(AccessController.jav
    a:125)
    	at
    java.security.AccessController.checkPermission(AccessControl
    ler.java:198)
    	at
    java.lang.SecurityManager.checkPermission(SecurityManager.ja
    va:563)
    	at
    com.ibm.websphere.security.auth.WSSubject.getRunAsSubject(WS
    Subject.java:397)
    	at web.RunAsServlet.performTask(RunAsServlet.java:39)
    	at web.BaseServlet.handleRequest(BaseServlet.java:79)
    	at web.BaseServlet.doGet(BaseServlet.java:49)
    	at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
    	at web.BaseServlet.service(BaseServlet.java:43)
    	at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
    
    the permission javax.security.auth.AuthPermission was
    already defined in the permissions.xml file, but the
    exception was still issued.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty - Security                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: AccessControlException issued even when *
    *                      permission was granted in the           *
    *                      permissions.xml file                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    For WebSphere Application Server Liberty, in some instances
    there is an AccessControlException issued for a permission that
    had been granted in the application's permissions.xml file.  For
    example, for the following AccessControlException,
    
    java.security.AccessControlException: Access denied
    ("javax.security.auth.AuthPermission"
    "wssecurity.getRunAsSubject")
    	at
    java.security.AccessController.throwACE(AccessController.java:12
    5)
    	at
    java.security.AccessController.checkPermission(AccessController.
    java:198)
    	at
    java.lang.SecurityManager.checkPermission(SecurityManager.java:5
    63)
    	at
    com.ibm.websphere.security.auth.WSSubject.getRunAsSubject(WSSubj
    ect.java:397)
    	at web.RunAsServlet.performTask(RunAsServlet.java:39)
    	at web.BaseServlet.handleRequest(BaseServlet.java:79)
    	at web.BaseServlet.doGet(BaseServlet.java:49)
    	at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
    	at web.BaseServlet.service(BaseServlet.java:43)
    	at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
    
    the permission javax.security.auth.AuthPermission was already
    defined in the permissions.xml file, but the exception was still
    issued.
    

Problem conclusion

  • The code was modified to prevent an AccessControlException from
    being issued when it was already granted to the application.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 17.0.0.1.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI73266

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-12-05

  • Closed date

    2016-12-13

  • Last modified date

    2016-12-13

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • R855 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 May 2022