-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
When org.jboss.as.naming.NamingContext checks {{JndiPermission}}s, it is not using the proper absolute name.
One example:
Failed permission check: permission ("org.jboss.as.naming.JndiPermission" "env/ejb/AEJBLocal" "lookup")
In this example, the name being checked is "env/ejb/AEJBLocal", where it should probably be "java:comp/env/ejb/AEJBLocal". The naming context name is being left off in the shuffle; the "absolute name" calculated by org.jboss.as.naming.NamingContext#getAbsoluteName() is still only relative to the naming context's own root.
- blocks
-
WFLY-504 Security Manager integration
- Closed