Types of authentication used

In this section you will be guided through different authentication methods you have to gain certain access to our resources. You can do it through the following three protocols:

OAuth

OAuth (Open Authorization) is an authorization protocol allowing users to grant limited access to resources without sharing their credentials directly. To gain this access, a user authorizes a third-party application to access specific resources on their behalf; the application receives an access token that allows it to interact with those resources at a particular time and with specific permissions.

Cloud	Egress IP	Connector
✅	Only for SaaS	Only for SaaS

We recommend using this method as it is more secure and simple.

You can check this section to know how to add repositories via OAuth.

SSH

SSH (Secure Shell) is a network protocol that provides a secure, encrypted connection to remote devices over the cloud. SSH connectivity is established through an authentication process that uses public and private key cryptography.

Cloud	Egress IP	Connector
✅	✅	✅

The following section describes how to add a git root with SSH credentials.

Adding a root with the SSH key

SSH keys enable you to connect to your repository server without a username and password. Here, you have to supply a Private Key. If you need to set up an SSH Key, we recommend reading this document: Use SSH keys to communicate with GitLab.

Go to the Scope section and click Add a new root. Here, you have two options: to add it through Oauth (Open Authorization) or manually. In this section, we will explain you manually, but if you want to see how to do it via Oauth, go to this link.
Click on the Add root manually button; you will get a popup window where you must enter the information of the new repository you want to add.

Note: When adding an SSH type URL, it will be automatically identified by entering the type in the Credential Type field.
When filling in all the fields, click the Confirm button, and the SSH input will appear in the Git Roots section.

Note: If you want to know what each field to fill in when creating a git root, you can go to the following link.

HTTPS

HTTPS (Hypertext Transfer Protocol Secure) provides a layer of security in data transmission. Using SSL/TLS encryption, HTTPS ensures that the information transferred between users and the repository is protected against possible threats, guaranteeing the data's confidentiality, integrity, and authenticity, maintaining a reliable and secure collaboration environment.

Also, we support the HTTP protocol but we recommend using HTTPS for secure connections and data protection.

Cloud	Egress IP	Connector
✅	✅	✅

The following section describes how to add a git root with HTTPS credentials.

Adding a root with the HTTPS (User and Password)

Cloning a repository via HTTPS is a simple and secure process by setting User and Password as credentials, giving access to the inputs.

Go to the Scope section and click Add a new root. Here, you have two options: to add it through Oauth (Open Authorization) or manually. In this section, we will explain you manually, but if you want to see how to do it via Oauth, go to this link.
Click on the Add root manually button; you will get a popup window where you must enter the information of the new repository you want to add

Note: When adding an HTTPS type URL, it will be automatically identified by entering the type in the Credential Type field.
When filling in all the fields, click the Confirm button, and the HTTPS input will appear in the Git Roots section.
It is important to note that the fields to be completed include "username" and "password." In some providers, the password field may be called "Personal Access Tokens," generating access to your code.