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

RemoteFailoverTestCase.testSecureStatelessFailover fails due to authorization

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Blocker
    • None
    • None
    • Security, Test Suite
    • None

    Description

      On the server, the authentication information seems OK. PicketBox is rejecting authorization, probably due to some change in Elytron integration.

      The stack trace looks like this:

      2017-06-26 21:45:30 testSecureStatelessFailover(org.jboss.as.test.clustering.cluster.ejb.remote.RemoteFailoverTestCase)  Time elapsed: 5.765 sec  <<< ERROR!
2017-06-26 21:45:30 javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract org.jboss.as.test.clustering.cluster.ejb.remote.bean.Result org.jboss.as.test.clustering.cluster.ejb.remote.bean.Incrementor.increment() of bean: SecureStatelessIncrementorBean is not allowed
2017-06-26 21:45:30     at org.jboss.as.ejb3.security.AuthorizationInterceptor.processInvocation(AuthorizationInterceptor.java:134)
2017-06-26 21:45:30     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
2017-06-26 21:45:30     at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
2017-06-26 21:45:30     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
2017-06-26 21:45:30     at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
2017-06-26 21:45:30     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
2017-06-26 21:45:30     at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
2017-06-26 21:45:30     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
2017-06-26 21:45:30     at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:57)
2017-06-26 21:45:30     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
2017-06-26 21:45:30     at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67)
2017-06-26 21:45:30     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
2017-06-26 21:45:30     at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
2017-06-26 21:45:30     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
2017-06-26 21:45:30     at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
2017-06-26 21:45:30     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
2017-06-26 21:45:30     at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60)
2017-06-26 21:45:30     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
2017-06-26 21:45:30     at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:256)
2017-06-26 21:45:30     at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:609)
2017-06-26 21:45:30     at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57)
2017-06-26 21:45:30     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
2017-06-26 21:45:30     at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
2017-06-26 21:45:30     at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198)
2017-06-26 21:45:30     at org.wildfly.security.auth.server.SecurityIdentity.runAsFunctionEx(SecurityIdentity.java:380)
2017-06-26 21:45:30     at org.jboss.as.ejb3.remote.AssociationImpl.invokeWithIdentity(AssociationImpl.java:480)
2017-06-26 21:45:30     at org.jboss.as.ejb3.remote.AssociationImpl.invokeMethod(AssociationImpl.java:475)
2017-06-26 21:45:30     at org.jboss.as.ejb3.remote.AssociationImpl.lambda$receiveInvocationRequest$0(AssociationImpl.java:183)
2017-06-26 21:45:30     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
2017-06-26 21:45:30     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
2017-06-26 21:45:30     at java.lang.Thread.run(Thread.java:745)

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFLY-9002 RemoteFailoverTestCase.testSecureStatelessFailover fails due to authorization

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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11337 Fix and re-enable RemoteFailoverTestCase

          • 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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9355 EJB cluster proxies are not failing over

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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11337 Fix and re-enable RemoteFailoverTestCase

          • 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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: