Save the CA Root certificate of the server's certificate to a file in one of the supported formats (the file is referred as below). These are generic Java application steps (not TeamCity-specific):
To enable HTTPS connections from Java clients, you need to install the server certificate (or your organization's certificate the server's certificate is signed by) into the JVM as a trusted certificate. If your certificate is not valid (is self-signed): To use Let's Encrypt-issued certificates, make sure to upgrade the JVM used by the client to the latest. If your certificate is valid (that is it was issues and signed by a well-known Certificate Authority like Verisign), then the Java clients should work with HTTPS without any additional configuration. To enable HTTPS connections from Java clients (TeamCity Agents, IntelliJ IDEA, Eclipse, and so on), see the section below for configuring the JVM installation used by the connecting application.Ĭonfiguring JVM Configuring client JVM for trusting server certificate After that, the Visual Studio Add-in should be able to connect by HTTPS. To enable HTTPS connections from the TeamCity Visual Studio Add-in, point your Internet Explorer to the TeamCity server using URL and import the server certificate into the browser. is not signed by a known Certificate Authority and likely to result in "PKIX path building failed: .SunCertPathBuilderException: unable to find valid certification path to requested target" error message) All you have to do is use links to the TeamCity server instead of If your certificate is not valid (is self-signed): (i.e.
it was signed by a well known Certificate Authority like Verisign), then TeamCity clients should work with HTTPS without any additional configuration. In the setup, make sure that the reverse proxy has correct configuration as per Set Up TeamCity behind a Proxy Server section. The most common and recommended approach for this is to set up a reverse proxy server like Nginx or Apache that provides HTTPS access for HTTP-only TeamCity server's Tomcat port. We assume that you have already configured HTTPS in your TeamCity web server. If you need to connect the TeamCity server to a service behind a self-signed certificate (for example, Git) or if you need to connect a TeamCity agent to the TeamCity server using the self-signed certificate, use trusted certificates configuration. This document describes how to configure Java applications to use HTTPS for communicating with the server.
0 kommentar(er)
