]
Darran Lofthouse commented on WFWIP-344:
----------------------------------------
This sounds to be the expected behaviour, there is an example in the wildfly jar plugin
project to active SSL so just sounds as though it is not activated.
Bootable JAR - SSL 8443 port doesn't work by default
----------------------------------------------------
Key: WFWIP-344
URL:
https://issues.redhat.com/browse/WFWIP-344
Project: WildFly WIP
Issue Type: Bug
Reporter: Marek Kopecky
Assignee: Jean Francois Denise
Priority: Blocker
Attachments: ssl-war.war
RFE jira: EAP7-1385
SSL 8443 port doesn't work by default on bootable jar
*Steps to reproduce:*
* start bootable jar (hollow jar) with jaxrs-server, microprofile-config, datasources,
h2-default-datasource layers (you can check the same on WF)
* deploy deployment with this simple deployment ([^ssl-war.war]):
{code:java}
@Path("/ssl")
public class SslResource {
@Path("/hello")
@GET
public String hello() {
return "Hello World!";
}
}
{code}
* Make HTTP call by this client (use [this
client.truststore|https://github.com/resteasy/Resteasy/blob/3.12/testsuit...]):
{code:java}
truststore = KeyStore.getInstance("jks");
try (InputStream in = new
FileInputStream("/home/path/client.truststore")) {
truststore.load(in, "123456".toCharArray());
}
resteasyClientBuilder = (ResteasyClientBuilder) ClientBuilder.newBuilder();
resteasyClientBuilder.setIsTrustSelfSignedCertificates(false);
resteasyClientBuilder = resteasyClientBuilder.disableTrustManager();
client = resteasyClientBuilder.trustStore(truststore).build();
Response response =
client.target("https://127.0.0.1:8443/ssl-war/ssl/hello").request().get();
System.out.println("Response status: " + response.getStatus() + "
(expected is 200)");
if (response.getStatus() == 200) {
System.out.println("Output: " +
response.readEntity(String.class));
}
{code}
* See the results:
** "Connection refused (Connection refused)" on bootable jar
** 200 response code on WF
cc: [~fburzigo], [~yersan], [~asoldano], [~ron_sigal]