March 28th 1 PM ET
Free Workshop: Escape the chaos of context-switching

Git Integration for Jira Self-Managed (Data Center/Server) Documentation

Manually connect to HTTPS git repositories with self-signed SSL certificates or other SSL issues

When connecting to a private HTTPS git repository, a problem may be caused by a custom (self-signed) certificate. Make sure to install the latest JRE and then change the JAVA_HOME of Jira server.

If the above solution doesn’t work, see below for the steps to workaround this issue:

  1. From your Jira Server, clone the repository manually using the git client.

    Example:

    cd /jira/home
    cd data/git-plugin
    git clone --mirror https://my-self-signed-repo/project.git
  2. Make sure the Jira user has access to the folder above.

  3. Configure the repository to disable verification of the SSL certificate:

    Run git config http.sslVerify false in the repository folder.

    Example:

    cd project.git
    git config http.sslVerify false
  4. Add repository via Connect wizard ➜ Advanced Setup.

  5. Set Repository root to the folder that was used in step 1.

  6. The clone will be kept up-to-date and the SSL verification issues will be ignored.

There are alternative solutions to make Java trust this certificate. Refer to the good articles from Atlassian which focuses on helping to resolve SSL Verification Issues:

  1. Unable to Connect to SSL Services due to PKIX Path Building Failed
  2. Connecting to SSL services

 

For related topics on connecting repositories from other git hosts, see Integration Guides.

 


Prev: Automatically connect to HTTPS git repositories with self-signed SSL certificates or other SSL issues

Next: Managing repository or integration configuration

Have feedback about this article? Did we miss something? Let us know!
On this page