HTTPS
Code Insight supports an anonymous or authenticated HTTPS protocol between the Git client (installed on the same machine as the Code Insight Scan Server) and the Git server, such as GitHub, GitLab, and Bitbucket, containing the repository to be synchronized to Code Insight.
HTTPS Configuration
Ensure that the SSL certificate verification between the Git client, installed on the same machine as the Code Insight Scan Server, and the Git server is successful. This verification might include importing the Git server certificate into the local cacert authority. Because the details of this process is outside the scope of Code Insight documentation, refer to the appropriate Git server or client documentation for further details.
In a trusted environment, one option to ease the integration process is to skip the SSL certificate validation step by running the following step from the machine running the Scan Server:
git config --global http.sslVerify false
URL Format
For an anonymous HTTPS protocol, use a URL similar to one of these:
| Type | Example |
|---|---|
| GitHub example | https://github\.com/myacct/Spoon\-Knife\.git |
| GitLab example | https://gitlab\.com/myacct/Spoon\-Knife\.git |
| Bitbucket example | https://bitbucket\.org/myacct/myquotefork\.git |
For authenticated HTTPS protocol, provide an account and password, separating them with a colon as shown in these examples:
| Type | Example |
|---|---|
| GitHub example | https://myacct:password@github\.com/myacct/Hello\-World\.git |
| GitLab example | https://myacct:password@gitlab\.com/myacct/Spoon\-Knife\.git |
| Bitbucket example | https://myacct:password@bitbucket\.org/myacct/bb101repo\.git |