This section explains how to enable https access for QuickBuild.
Follow document of your choosed application server to enable
https. By default, QuickBuild runs on top of tomcat which is
available in the tomcat sub directory under the
QuickBuild installation directory. Document of configuring https for
tomcat can be found here.
Edit web.xml (by default, it is located
in directory <QuickBuild install
dir>/web/WEB-INF) to uncomment below section:
<security-constraint>
<web-resource-collection>
<web-resource-name>all</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>Change to administration menu, and update value of QuickBuild servlet URL system setting to reflect the https url.
For client applications using QuickBuild's remote API, if the exception SSLHandshakeException is thrown with message "unable to find valid certification path to requested target", please follow instructions here to trust certificate of https-enabled QuickBuild server.
For QuickBuild instances (could be the same QuickBuild instance as the https-enabled one) who interacts with the https-enabled instance, if the exception SSLHandshakeException is thrown with message "unable to find valid certification path to requested target", please follow instructions here to trust certificate of https-enabled QuickBuild server. Below is some examples of the interations:
Promote build to certain configuration of the https-enabled QuickBuild instance.
Trigger build in certain configuration of the https-enabled QuickBuild instance through step "Trigger build in another configuration".
Depends on certain configuration of the https-enabled QuickBuild instance through the repository of type QuickBuild.