This section guides you through the different authentication methods available for Fluid Attacks to access your repositories:

• OAuth
• SSH
• HTTPS

OAuth

Available for Azure, Bitbucket, GitHub, and GitLab

Using the OAuth protocol is advised, as it is more secure and simple than the two alternatives.

OAuth (Open Authorization) is an authorization protocol that allows users to grant applications limited access to their resources without directly sharing their credentials. Once authorized, the application receives an access token, which is a string representing the granted permissions. This token allows the application to access the specified resources for a certain period and within the defined scope of permissions, without ever needing the user's credentials.

The following are some key benefits of OAuth:

1. Enhanced security: Users do not expose their credentials to third-party applications.
   
2. Granular control: Users can choose which resources to share and revoke access at any time.
   
3. Improved user experience: OAuth provides a simplified authorization process without the need for multiple logins.

Learn to use this option by reading Import repositories fast and safely with OAuth.

OAuth is supported for connections as follows:

Cloud	Egress IP	Connector
✅	Only for SaaS	Only for SaaS

SSH

SSH (Secure Shell) is a network protocol that provides a secure, encrypted connection to remote devices over the cloud. It is primarily used for remote login and command-line execution but also supports file transfer, port forwarding, and other secure network services. SSH connectivity is established through an authentication process that uses public and private key cryptography.

The following are some key benefits of SSH:

1. Strong authentication: SSH typically employs public-key cryptography for authentication, where a user generates a pair of keys: a private key (kept secret) and a public key (shared with the server). This ensures that only someone with the private key can access the server.
   
2. Encryption: All communication over SSH is encrypted, protecting data from eavesdropping and tampering.
   
3. Integrity: SSH includes mechanisms to verify the integrity of transmitted data, ensuring that it has not been modified in transit.

Learn to use this option by reading Add a root with an SSH key.

SSH is supported for connections as follows:

Cloud	Egress IP	Connector
✅	✅	✅

HTTPS

1. Data encryption: HTTPS prevents eavesdropping and man-in-the-middle attacks.
   
2. Data integrity: HTTPS ensures that the data received has not been altered in transit.
   
3. Website identity verification: HTTPS verifies the identity of the website, protecting against phishing and other fraudulent activities.
   

Learn to use this option by reading Add a root with user and password.

Note: While Fluid Attacks also supports the HTTP protocol, using HTTPS is strongly recommended for secure connections and data protection.