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

MissingMethodPermissionsDefaultAllowedTestCase and MissingMethodPermissionsTestCase fail when run with the Elytron profile enabled

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.1.0.ER2
    • 7.1.0.DR19, 7.1.0.ER1
    • EJB, Security
    • None
    • Blocks Testing
    • Hide

      Run the following command in WildFly Test Suite Integration/Basic module with Elytron profile:

      mvn clean test -Dtest=MissingMethodPermissionsDefaultAllowedTestCase -Delytron -Dwildfly.tmp.enable.elytron.profile.tests

      The test deployment will have no security domain associated with it and fall back to CLM authentication, therefore failing the tests.

      Show
      Run the following command in WildFly Test Suite Integration/Basic module with Elytron profile: mvn clean test -Dtest=MissingMethodPermissionsDefaultAllowedTestCase -Delytron -Dwildfly.tmp.enable.elytron.profile.tests The test deployment will have no security domain associated with it and fall back to CLM authentication, therefore failing the tests.

    Description

      Suppose a deployment with EJB with security related annotations (for example @RolesAllowed) but without a @SecurityDomain annotation. If the EAP running the deployment has attribute default-security-domain in /subsystem=ejb3 defined, this will be used for any bean without security domain used in deployment. This works with PicketBox domains, however, if an Elytron security domain is defined as default, no such domain will be associated with the deployment.

      This also causes failure of org.jboss.as.test.integration.ejb.security.missingmethodpermission.*TestCase tests in integration/basic module in test suite.

      Attachments

        Issue Links

          causes

          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
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-8956 MissingMethodPermissionsDefaultAllowedTestCase and MissingMethodPermissionsTestCase fail when run with the Elytron profile enabled

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related to

          Task - Represents a small unit of work that is not end-user facing. JBEAP-11560 Fix tests which currently fail with -Dwildfly.tmp.enable.elytron.profile.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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: