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

EJB security tests are failing in AS TS with Elytron profile

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.0.CR1
    • 7.1.0.DR12, 7.1.0.DR13, 7.1.0.DR14, 7.1.0.DR15, 7.1.0.DR16, 7.1.0.DR17, 7.1.0.DR18, 7.1.0.DR19, 7.1.0.ER1
    • Test Suite
    • None

    Description

      Many tests under org.jboss.as.test.integration.ejb.security package are failing when using "-Delytron" argument.

      cd testsuite/integration/basic
mvn clean test -Dtest=org.jboss.as.test.integration.ejb.security.**.* -Delytron
...
Failed tests: 
  https://issues.jboss.org/browse/JBEAP-9080#InherritanceAnnSFSBTestCase.testSingleMethodAnnotationsUser1:71->AnnSBTest.testSingleMethodAnnotationsUser1Template:156->AnnSBTest.lambda$testSingleMethodAnnotationsUser1Template$1:169 EJBAccessException not expected
  InherritanceAnnSFSBTestCase.testSingleMethodAnnotationsUser2:76->AnnSBTest.testSingleMethodAnnotationsUser2Template:221->AnnSBTest.lambda$testSingleMethodAnnotationsUser2Template$2:242 EJBAccessException not expected
  InherritanceAnnSLSBTestCase.testSingleMethodAnnotationsUser1:70->AnnSBTest.testSingleMethodAnnotationsUser1Template:156->AnnSBTest.lambda$testSingleMethodAnnotationsUser1Template$1:169 EJBAccessException not expected
  InherritanceAnnSLSBTestCase.testSingleMethodAnnotationsUser2:75->AnnSBTest.testSingleMethodAnnotationsUser2Template:221->AnnSBTest.lambda$testSingleMethodAnnotationsUser2Template$2:242 EJBAccessException not expected
  InjectionAnnSFSBtoSFSBTestCase.testSingleMethodAnnotationsUser1:70->AnnSBTest.testSingleMethodAnnotationsUser1Template:156->AnnSBTest.lambda$testSingleMethodAnnotationsUser1Template$1:169 EJBAccessException not expected
  InjectionAnnSFSBtoSFSBTestCase.testSingleMethodAnnotationsUser2:75->AnnSBTest.testSingleMethodAnnotationsUser2Template:221->AnnSBTest.lambda$testSingleMethodAnnotationsUser2Template$2:242 EJBAccessException not expected
  InjectionAnnSFSBtoSLSBTestCase.testSingleMethodAnnotationsUser1:70->AnnSBTest.testSingleMethodAnnotationsUser1Template:156->AnnSBTest.lambda$testSingleMethodAnnotationsUser1Template$1:169 EJBAccessException not expected
  InjectionAnnSFSBtoSLSBTestCase.testSingleMethodAnnotationsUser2:75->AnnSBTest.testSingleMethodAnnotationsUser2Template:221->AnnSBTest.lambda$testSingleMethodAnnotationsUser2Template$2:242 EJBAccessException not expected
  InjectionAnnSLSBtoSFSBTestCase.testSingleMethodAnnotationsUser1:70->AnnSBTest.testSingleMethodAnnotationsUser1Template:156->AnnSBTest.lambda$testSingleMethodAnnotationsUser1Template$1:169 EJBAccessException not expected
  InjectionAnnSLSBtoSFSBTestCase.testSingleMethodAnnotationsUser2:75->AnnSBTest.testSingleMethodAnnotationsUser2Template:221->AnnSBTest.lambda$testSingleMethodAnnotationsUser2Template$2:242 EJBAccessException not expected
  InjectionAnnSLSBtoSLSBTestCase.testSingleMethodAnnotationsUser1:72->AnnSBTest.testSingleMethodAnnotationsUser1Template:156->AnnSBTest.lambda$testSingleMethodAnnotationsUser1Template$1:169 EJBAccessException not expected
  InjectionAnnSLSBtoSLSBTestCase.testSingleMethodAnnotationsUser2:77->AnnSBTest.testSingleMethodAnnotationsUser2Template:221->AnnSBTest.lambda$testSingleMethodAnnotationsUser2Template$2:242 EJBAccessException not expected
  SingleMethodsAnnSFSBTestCase.testSingleMethodAnnotationsUser1:70->AnnSBTest.testSingleMethodAnnotationsUser1Template:156->AnnSBTest.lambda$testSingleMethodAnnotationsUser1Template$1:169 EJBAccessException not expected
  SingleMethodsAnnSFSBTestCase.testSingleMethodAnnotationsUser2:75->AnnSBTest.testSingleMethodAnnotationsUser2Template:221->AnnSBTest.lambda$testSingleMethodAnnotationsUser2Template$2:242 EJBAccessException not expected
  SingleMethodsAnnSLSBTestCase.testSingleMethodAnnotationsUser1:70->AnnSBTest.testSingleMethodAnnotationsUser1Template:156->AnnSBTest.lambda$testSingleMethodAnnotationsUser1Template$1:169 EJBAccessException not expected
  SingleMethodsAnnSLSBTestCase.testSingleMethodAnnotationsUser2:75->AnnSBTest.testSingleMethodAnnotationsUser2Template:221->AnnSBTest.lambda$testSingleMethodAnnotationsUser2Template$2:242 EJBAccessException not expected
  RunAsTestCaseEJBMDB.testSendMessage:152 null
Tests in error: 
  RunAsPrincipalTestCase.org.jboss.as.test.integration.ejb.security.RunAsPrincipalTestCase » Deployment
  MissingMethodPermissionsDefaultAllowedTestCase.testAllowAccessByDefaultForMethodsMissingPermissions:205 » EJBAccess
  MissingMethodPermissionsDefaultAllowedTestCase.testAllowAccessForMethodsMissingPermissions:164 » EJBAccess
  MissingMethodPermissionsDefaultAllowedTestCase.testDenyAccessForMethodsMissingPermissions:183 » EJBAccess
  MissingMethodPermissionsTestCase.testAllowAccessForMethodsMissingPermissions:116 » EJBAccess
  MissingMethodPermissionsTestCase.testDenyAccessByDefaultForMethodsMissingPermissions:157 » EJBAccess
  MissingMethodPermissionsTestCase.testDenyAccessForMethodsMissingPermissions:135 » EJBAccess
  RunAsTestCaseEJBMDB.testEjb » EJBAccess WFLYEJB0364: Invocation on method: pub...
  SingletonSecurityTestCase.testInvocationOnSecuredMethodWithCorrectRole:79 » EJBAccess

Tests run: 91, Failures: 17, Errors: 9, Skipped: 1

      Sample stack trace of the failure:

      java.lang.AssertionError: EJBAccessException not expected
        at org.junit.Assert.fail(Assert.java:88)
        at org.jboss.as.test.integration.ejb.security.AnnSBTest.lambda$testSingleMethodAnnotationsUser1Template$1(AnnSBTest.java:169)
        at org.wildfly.common.context.Contextual.runCallable(Contextual.java:127)
        at org.jboss.as.test.integration.ejb.security.AnnSBTest.testSingleMethodAnnotationsUser1Template(AnnSBTest.java:156)
        at org.jboss.as.test.integration.ejb.security.InherritanceAnnSFSBTestCase.testSingleMethodAnnotationsUser1(InherritanceAnnSFSBTestCase.java:71)

      Attachments

        Issue Links

          blocks

          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 blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9752 ClientLoginModule does not work with Elytron secured EJBs for In-VM Calls e.g. Servlet to Bean or Bean to Bean

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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-12488 AuthenticationTestCase fails when server IP address is not bound to loopback in 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-11933 Security identity not propagated into asynchronous task (elytron)

          • 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 caused by

          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

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

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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11452 @RunAs role authorization from the first invoker of @Singleton bean is propagated through the @PostConstruct method of @Singleton bean with Elytron

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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11393 Fix AuthenticationTestCase and GetCallerPrincipalTestCase for Elytron and unignore it

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9198 RunAsPrincipalTestCase fails to deploy when Elytron profile is used

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

              mjurc@redhat.com Michal Jurc
              josef.cacek@gmail.com Josef Cacek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: