Arquillian Remote Domain Container With HTTPS Only Configured On Wildfly Server

[fearghalom]

I'm wondering is it possible to get Arquillian tests to run with a remote domain container when the http listener has been disabled on the Wildfly instance under test? When I enable the http-listener, the tests execute successfully.
I debugged through the Arquillian code and noticed that the protocol seems to be hardcoded to HTTP in org.jboss.as.arquillian.container.domain.ManagementClient when determining the subsystem URI.

[jamezp]

The management HTTP does need to be listening. There is a in 4.0.0.Alpha5 and 5.0.0.Alpha5 to use a different binding name https://issues.redhat.com/browse/WFARQ-31. You can add the socketBindingGroup property to your arquillian.xml.

[fearghalom]

That's great, thanks James for addressing this so promptly

[jamezp]

I forgot to mention last week that WildFly Arquillian 4.0.0.Alpha6 for Jakarta EE 8 and WildFly Arquillian 5.0.0.Alpha6 for Jakarta EE 9/10 was released. It includes the support for overriding the socket-binding in domain.

The property name was changed to socketBindingName. Also 5.0.0.Alpha6 now requires Java 11.

[fearghalom]

I upgraded to v4.0.0.Alpha6 and configured the arquillian.xml as follows:

<?xml version="1.0" encoding="UTF-8"?>

<arquillian xmlns="http://jboss.org/schema/arquillian"
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
            xsi:schemaLocation="http://jboss.org/schema/arquillian http://jboss.org/schema/arquillian/arquillian_1_0.xsd">

    <container qualifier="jboss" default="true">
        <configuration>
            <property name="socketBindingName">https</property>
            <property name="protocol">https</property>
        </configuration>
    </container>
</arquillian>

However, I'm getting the following exception now:

java.net.SocketException: Unexpected end of file from server
	at java.base/sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:862)
	at java.base/sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:689)
	at java.base/sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:859)
	at java.base/sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:689)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1615)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1520)
	at java.base/java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:527)
	at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.execute(ServletMethodExecutor.java:168)
	at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor$1.run(ServletMethodExecutor.java:221)
	at java.base/java.util.TimerThread.mainLoop(Timer.java:556)
	at java.base/java.util.TimerThread.run(Timer.java:506)

Is there more I need to configure to get this to work? Does the servlet protocol support authentication?

[jamezp]

I don't think it handles authentication, no. What kind of authentication would you want to support? It's something to be considered for sure.

[fearghalom]

Basic authentication would do to begin with.