Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-24199

[GSS](7.4.z) WFLY-17316 - SecurityContext callerPrincipal not set with Asynchronous tagged EJB

    XMLWordPrintable

Details

    Description

      The JSR 345: Enterprise JavaBeans 3.2 specification defines that propagation must behave exactly the same behavior between sync and async. When using the SecurityContext.getCallerPrincipal, the used Eclipse Soteria implementation of the Java EE Security API Specification is delegating to EJBContext.getCallerPrincipal which obtains the custom principal correctly. This principal is returned only if it is of CallerPrincipal type. This fix is to return the principal from EJBContext whether it is of type CallerPrincipal or not.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFLY-17316 SecurityContext callerPrincipal not set with Asynchronous tagged EJB

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-24200 [GSS](8.0.z) SecurityContext callerPrincipal not set with Asynchronous tagged EJB

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-24207 (7.4.z) Upgrade Soteria from 1.0.1.redhat-00002 to 1.0.1.redhat-00003

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              dvilkola@redhat.com Diana Krepinska
              rhn-support-jbaesner Joerg Baesner
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: