Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-136

JNDI name permission checking is wrong

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 8.0.0.Alpha1
    • None
    • Naming
    • None

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              emartins@redhat.com Eduardo Martins
              dlloyd@redhat.com David Lloyd
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: