Types of authentication

Last updated: Sep 30, 2026

---

This page describes the authentication methods that Fluid Attacks can use to access your repositories:

• OAuth
• SSH
• HTTPS

OAuth

OAuth (Open Authorization) is an authorization protocol. With OAuth, users give an application access to some of their resources. The users do not share their credentials with the application.

After the user authorizes the application, the application receives an access token. The token is a string that represents the granted permissions. With this token, the application accesses the given resources for a defined time and in the defined scope. The credentials of the user are not necessary for the application.

Primary benefits of OAuth:

• Enhanced security: Users do not expose their credentials to third-party applications.
• Granular control: Users select the resources to share. They can revoke the access at all times.
• Improved user experience: The authorization procedure is simple, and many logins are not necessary.

OAuth support by connection:

SSH

SSH (Secure Shell) is a network protocol. It gives a secure, encrypted connection to remote devices through the cloud. Its primary uses are remote login and command-line execution. It also supports file transfer, port forwarding, and other secure network services. SSH authenticates the connection with public and private key cryptography.

Primary benefits of SSH:

• Strong authentication: SSH uses public-key cryptography. The user makes a pair of keys: a private key, which stays secret, and a public key, which goes to the server. Only the owner of the private key can access the server.
• Encryption: SSH encrypts all communication. This protects the data from eavesdropping and tampering.
• Integrity: SSH checks the integrity of the transmitted data. This makes sure that nobody changed the data in transit.

SSH support by connection:

HTTPS

HTTPS (Hypertext Transfer Protocol Secure) is an extension of the Hypertext Transfer Protocol (HTTP). It gives secure communication through a computer network.

HTTPS encrypts the communication channel with Transport Layer Security (TLS). Older versions used its predecessor, Secure Sockets Layer (SSL). The encryption protects the information between the users and the repository. It keeps the data confidential and complete, and it confirms the source. The result is a reliable and secure collaboration environment.

Primary benefits of HTTPS:

• Data encryption: HTTPS prevents eavesdropping and man-in-the-middle attacks.
• Data integrity: HTTPS makes sure that nobody changed the data in transit.
• Website identity verification: HTTPS verifies the identity of the website. This protects against phishing and other fraud.

HTTPS support by connection: