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

ClientLoginModule does not work with Elytron secured EJBs for In-VM Calls e.g. Servlet to Bean or Bean to Bean

    XMLWordPrintable

Details

    Description

      ClientLoginModule does not establish client caller identity and credentials when used to invoke EJBs backed by Elytron application-security-domain.

      This issue affects easy migration to Elytron as no instructions to replace this have been provided as well as AS TS testing with Elytron profile since nearly every test case in org.jboss.as.test.integration.ejb.remote.security uses CLM to establish identity/credentials.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9080 EJB security tests are failing in AS TS with Elytron profile

          • 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.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9051 Tracking JIRA for tests failing with Elytron profile in AS TS

          • 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. WFLY-8562 Add a test utility to ensure that tests use the ClientLoginModule approach for PicketBox deployments and the Elytron approach for Elytron deployments and update all affected tests

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11454 In-VM calls with authenticated SecurityIdentity.runAs(Callable c) fail to authorise for asynchronous EJB calls

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-10576 Server reload missing in tearDown method of EjbElytronDomainSetup

          • 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.
          • Verified

          Activity

            People

              fjuma1@redhat.com Farah Juma
              mjurc@redhat.com Michal Jurc
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: