The SSL connection issue

[hantsy]

I tried to start GlassFish via Docker for Arquillian tests, but failed to connect to the DAS URL due to an SSL connection issue.

But there is NO such a problem when I start it manually or use the cargo Maven plugin.

[OndroMih]

Can you give us an example project?

[hantsy]

I found this line https://github.com/eclipse-ee4j/glassfish.docker/blob/main/images/server/8.0.2/Dockerfile#L75, which could enable a secure connection. It caused a REDIRECT action when connecting to the DAS URL. Check: https://github.com/hantsy/jakartaee11-starter-boilerplate/actions/runs/31601464969/job/94129662792

I refactored some code in my arquillian-glassfish and added redirection support like this: https://github.com/hantsy/arquillian-glassfish/blob/master/glassfish-common/src/main/java/org/jboss/arquillian/container/glassfish/client/GlassFishRestClient.java#L88. When connecting to the DAS URL, it displays a certificate issue, but I changed the code to use the Cargo Maven plugin to start a running server.

I can prepare a new PR later to reproduce the issue later.

[hantsy]

OK, I got the solution in the tests from this project and overcame the HTTPS connection issue via hantsy/arquillian-glassfish#93

But I hope there is an ENV variable in Docker to decide whether to enable a secure connection to the admin.

[OndroMih]

Yes, this is an intentional behavior in Docker. As Docker DAS is accessed from a hist system, it's a "remote" connection and GlassFish won't allow it over plain HTTP. Secure admin enables the secure admin to be able to access the Admin Console over HTTPS at https://localhost:4848.

We'll review the enhancement for the Arquillian connector to switch to HTTPS, thanks for that.