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

Deployment overlay tests are failing in AS TS with Elytron profile

    XMLWordPrintable

Details

    Description

      The tests in org.jboss.as.test.integration.deployment.deploymentoverlay package are failing when using "-Delytron" argument. 

      org.jboss.as.test.integration.deployment.deploymentoverlay.ear.OverlayExistingResourceTestCase
org.jboss.as.test.integration.deployment.deploymentoverlay.ear.OverlayNonExistingResourceTestCase
org.jboss.as.test.integration.deployment.deploymentoverlay.jar.OverlayExistingResourceTestCase
org.jboss.as.test.integration.deployment.deploymentoverlay.jar.OverlayNonExistingResourceTestCase
org.jboss.as.test.integration.deployment.deploymentoverlay.war.OverlayExistingResourceTestCase
org.jboss.as.test.integration.deployment.deploymentoverlay.war.OverlayNonExistingResourceTestCase

      There is a problem with SASL authentiacation, but this original exception is hidden by failure in final section (removing deployment-overlay).

      Updated

      When I add programmatic Elytron authentication into the test, then it passes. E.g.

      @Test
public void testOverlayAC() throws Exception {
    AuthenticationContext.empty()        
        .with(MatchRule.ALL,
            // just set username/password into AuthenticationConfiguration
            AuthenticationConfiguration.EMPTY.useName("user1").usePassword("password1"))
        // and run original test method
        .runExConsumer(s -> testOverlay(), null);
}

      When I try to add wildfly-config.xml into AS TS module resources, then Arquillian doesn't recognize, the server is started and fails on server-start timeout.

      The stack-trace for the hidden problem:

      FAILURE! - in org.jboss.as.test.integration.deployment.deploymentoverlay.war.OverlayExistingResourceTestCase
testOverlay(org.jboss.as.test.integration.deployment.deploymentoverlay.war.OverlayExistingResourceTestCase)  Time elapsed: 0.353 sec  <<< ERROR!
javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed:
   JBOSS-LOCAL-USER: Server rejected authentication
	at org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:110)
	at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:414)
	at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:239)
	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
	at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
	at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
	at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
	at ...asynchronous invocation...(Unknown Source)
	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:464)
	at org.jboss.remoting3.FutureConnection.getConnection(FutureConnection.java:117)
	at org.jboss.remoting3.FutureConnection.init(FutureConnection.java:77)
	at org.jboss.remoting3.FutureConnection.get(FutureConnection.java:152)
	at org.jboss.remoting3.EndpointImpl.doGetConnection(EndpointImpl.java:406)
	at org.jboss.remoting3.EndpointImpl.getConnection(EndpointImpl.java:340)
	at org.jboss.remoting3.UncloseableEndpoint.getConnection(UncloseableEndpoint.java:55)
	at org.wildfly.naming.client.remote.RemoteNamingProvider.lambda$new$0(RemoteNamingProvider.java:65)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentity(RemoteNamingProvider.java:107)
	at org.jboss.ejb.protocol.remote.RemoteEJBReceiver.getConnection(RemoteEJBReceiver.java:158)
	at org.jboss.ejb.protocol.remote.RemoteEJBReceiver.processInvocation(RemoteEJBReceiver.java:115)
	at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:316)
	at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:70)
	at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:319)
	at org.jboss.ejb.client.EJBInvocationHandler.lambda$invoke$0(EJBInvocationHandler.java:160)
	at org.jboss.ejb.client.EJBClientContext.performLocatedAction(EJBClientContext.java:393)
	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:150)
	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:100)
	at com.sun.proxy.$Proxy21.fetchResource(Unknown Source)
	at org.jboss.as.test.integration.deployment.deploymentoverlay.war.OverlayExistingResourceTestCase.testOverlay(OverlayExistingResourceTestCase.java:70)

      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-9425 Make anonymous EJB authn possible in Elytron - Get JBOSS_LOCAL_USER to behave quietly again

          • 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-9426 Make anonymous EJB authn possible in Elytron - Ensure the default Principal name is one compatible with the servers configuration

          • 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-9469 Fix deployment overlay tests to not hide authentication problems

          • 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

              josef.cacek@gmail.com Josef Cacek (Inactive)
              josef.cacek@gmail.com Josef Cacek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: