docs/translations/ru-RU/content/github/authenticating-to-github/about-authentication-to-github.md

title, intro, versions

title	intro	versions
About authentication to GitHub	You can securely access your account's resources by authenticating to {{ site.data.variables.product.product_name }}, using different credentials depending on where you authenticate.	free-pro-team enterprise-server * *

About authentication to {{ site.data.variables.product.prodname_dotcom }}

To keep your account secure, you must authenticate before you can access certain resources on {{ site.data.variables.product.product_name }}. When you authenticate to {{ site.data.variables.product.product_name }}, 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 {{ site.data.variables.product.product_name }} in a variety of ways: in the browser, via {{ site.data.variables.product.prodname_desktop }} or another desktop application, with the API, or via the command line. Each way of accessing {{ site.data.variables.product.product_name }} supports different modes of authentication.

• Username and password with two-factor authentication
• Personal access token
• Ключ SSH

Authenticating in your browser

You can authenticate to {{ site.data.variables.product.product_name }} in your browser in different ways.

• Username and password only
  • You'll create a password when you create your user account on {{ site.data.variables.product.product_name }}. We recommend that you use a password manager to generate a random and unique password. For more information, see "Creating a strong password."
• Two-factor authentication (2FA) (recommended)
  • If you enable 2FA, we'll also prompt you to provide a code that's generated by an application on your mobile device or sent as a text message (SMS) after you successfully enter your username and password. For more information, see "Accessing {{ site.data.variables.product.prodname_dotcom }} using two-factor authentication."
  • In addition to authentication with a mobile application or a text message, you can optionally add a secondary method of authentication with a security key using WebAuthn. For more information, see "Configuring two-factor authentication using a security key."

Authenticating with {{ site.data.variables.product.prodname_desktop }}

You can authenticate with {{ site.data.variables.product.prodname_desktop }} using your browser. For more information, see "Authenticating to {{ site.data.variables.product.prodname_dotcom }}."

Authenticating with the API

You can authenticate with the {{ site.data.variables.product.product_name }} 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 {{ site.data.variables.product.prodname_github_apps }}."

Authenticating with the command line

You can access repositories on {{ site.data.variables.product.product_name }} 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 "Which remote URL should I use?"

• You can work with all repositories on {{ site.data.variables.product.product_name }} over HTTPS, even if you are behind a firewall or proxy. Every time you use Git to authenticate with {{ site.data.variables.product.product_name }}, you'll be prompted to enter your credentials to authenticate with {{ site.data.variables.product.product_name }}, unless you cache them with a credential helper. {{ site.data.reusables.user_settings.password-authentication-deprecation }}

• You can work with all repositories on {{ site.data.variables.product.product_name }} over SSH, although firewalls and proxys might refuse to allow SSH connections. Using SSH requires you to generate an SSH public/private keypair on your local machine and add the public key to your {{ site.data.variables.product.product_name }} account. Every time you use Git to authenticate with {{ site.data.variables.product.product_name }}, you'll be prompted to enter your SSH key passphrase, unless you've stored the key. For more information, see "Generating a new SSH key and adding it to the ssh-agent."

{% if currentVersion == "free-pro-team@latest" %}To use a personal access token or SSH key to access resources owned by an organization that uses SAML single sign-on, you must also authorize the personal token or SSH key. For more information, see "Authorizing a personal access token for use with SAML single sign-on" or "Authorizing an SSH key for use with SAML single sign-on."{% endif %}