About authentication to GitHub
To keep your account secure, you must authenticate before you can access resources on GitHub AE. When you authenticate to GitHub AE, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be.
You can access your resources in GitHub AE in a variety of ways: in the browser, via GitHub Desktop or another desktop application, with the API, or via the command line. Each way of accessing GitHub AE supports different modes of authentication.
- Your identity provider (IdP)
- Personal access token
- SSH key
Authenticating in your browser
You can authenticate to GitHub AE in your browser using your IdP. For more information, see "About authentication with SAML single sign-on."
Authenticating with GitHub Desktop
You can authenticate with GitHub Desktop using your browser. For more information, see "Authenticating to GitHub."
Authenticating with the API
You can authenticate with the API in different ways.
- Personal access tokens
- In limited situations, such as testing, you can use a personal access token to access the API. Using a personal access token enables you to revoke access at any time. For more information, see "Creating a personal access token."
- Web application flow
- For OAuth Apps in production, you should authenticate using the web application flow. For more information, see "Authorizing OAuth Apps."
- GitHub Apps
- For GitHub Apps in production, you should authenticate on behalf of the app installation. For more information, see "Authenticating with GitHub Apps."
Authenticating with the command line
You can access repositories on GitHub AE from the command line in two ways, HTTPS and SSH, and both have a different way of authenticating. The method of authenticating is determined based on whether you choose an HTTPS or SSH remote URL when you clone the repository. For more information about which way to access, see "About remote repositories."
HTTPS
You can work with all repositories on GitHub AE over HTTPS, even if you are behind a firewall or proxy.
If you authenticate with GitHub CLI, you can either authenticate with a personal access token or via the web browser. For more information about authenticating with GitHub CLI, see gh auth login.
If you authenticate without GitHub CLI, you must authenticate with a personal access token. When Git prompts you for your password, enter your personal access token (PAT) instead. For more information, see "Creating a personal access token." Every time you use Git to authenticate with GitHub AE, you'll be prompted to enter your credentials to authenticate with GitHub AE, unless you cache them a credential helper.
SSH
You can work with all repositories on GitHub AE over SSH, although firewalls and proxys might refuse to allow SSH connections.
If you authenticate with GitHub CLI, the CLI will find SSH public keys on your machine and will prompt you to select one for upload. If GitHub CLI does not find a SSH public key for upload, it can generate a new SSH public/private keypair and upload the public key to your account on GitHub AE. Then, you can either authenticate with a personal access token or via the web browser. For more information about authenticating with GitHub CLI, see gh auth login.
If you authenticate without GitHub CLI, you will need to generate an SSH public/private keypair on your local machine and add the public key to your account on GitHub AE. For more information, see "Generating a new SSH key and adding it to the ssh-agent." Every time you use Git to authenticate with GitHub AE, you'll be prompted to enter your SSH key passphrase, unless you've stored the key.