HTTPS vs SSH Authentication

Updated 3 weeks ago by Copado Solutions

HTTPS

  1. Copy the repository HTTPS URL from your Git provider.
  2. In Copado, create a new Git Repository record and paste the HTTPS URL into the URI field.
  3. Fill in the Username and Password fields and then save the record. If you’re using Github, the combination has to be user and personal access token, for more information, please review the following article Token authentication requirements for Git operations.
If you are running a hosted Git repository (not in the Cloud), make sure Port 443 is open. If you have IP Restrictions / Firewall / Layer 7, make sure the Copado IP addresses can access the Git repository's URL. Check out the article IP Addresses for more information.

AWS CodeCommit To connect CodeCommit repositories, copy the HTTPS clone URL provided in the AWS Console, and then use your HTTPS Git credentials.

If you are an Azure DevOps user with a personal access token, you can configure your Git repository record in Copado. To do this, use the HTTPS authentication and add this token as the password.
If you are using Two-Factor Authentication in your Git repository, you will need to create a token within your repository.

SSH

  1. From your Git provider, copy the SSH URL.
  2. In Copado, create a new Git Repository record and paste the SSH URL into the URI field, then save the record.
  3. Now you need to create a new pair of keys. To do so, click on Create SSH Keys.
  4. Scroll down to the Current Keys related list.
  5. Click on the View link next to the id_rsa.pub file and copy the content.
  6. On your Git provider site, add the Public Key (id_rsa.pub).

If you are running a hosted Git repository (not in the Cloud), make sure Port 22 is open. IP restrictions are not supported for SSH.


How did we do?