[ https://issues.jboss.org/browse/RFPL-3837?page=com.atlassian.jira.plugin.... ] Matej Novotny resolved RFPL-3837. --------------------------------- Fix Version/s: 4.5.7 Resolution: Done HTTPS testing should be working now. I only included smoke tests on Jenkins ({{-Dsmoke}}) in order to cut down run time. A little insight in how things work: * When settings up an SLL connection in Wilfdly, one can follow tutorials such as [this one| http://blog.coffeebeans.at/?p=933] ** That is truly all you need to connect to {{https://localhost:8443}} and see that it works ** The required standalone.xml file is generated and fetched from our {{build-resources}} sub-project ** Due to RF-14056 release jobs cannot run https testing atm * Browser will likely scream at you by the time you try, hence FF profile is needed. ** The only purpose is to make a security exception for {{localhost}} ** In order to manage profiles close all FF windows and run FF via terminal as {{firefox -P}} * Jenkins makes use of a so called 'truststore', it is not needed locally ** From what I understood this contains a certificate of a third party, so basically it defines who is trustworthy ** It is uploaded and ready on Jenkins In order to see all the switches you need to make it run, see Jenkins job mentioned in issue description. -- This message was sent by Atlassian JIRA (v6.3.15#6346)