You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 21, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: docs/getting-started/authenticating-to-github.md
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,10 +7,14 @@ Before you authenticate, you must already have a GitHub or GitHub Enterprise acc
7
7
- For more information on creating a GitHub account, see "[Signing up for a new GitHub account](https://help.github.com/articles/signing-up-for-a-new-github-account/)".
8
8
- For a GitHub Enterprise account, contact your GitHub Enterprise site administrator.
9
9
10
-
> **Note:** If your organization is on the [Business plan](https://help.github.com/articles/organization-billing-plans) and has enabled SAML single sign-on, or an [Enterprise account] you must create and authorize a personal access token to access protected content. For more information on creating personal access tokens, see "[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line). The required scopes for the personal access token are: `user`, `repo`, `gist`, and `write:public_key`.
10
+
> **Note:** If your organization is on the [Business plan](https://help.github.com/articles/organization-billing-plans) and has enabled SAML single sign-on, you must create and authorize a personal access token to access protected content.
11
+
>You will also need to create a personal access token for signing in with GitHub Enterprise if your version is less than 2.12.2 and username/password login is disabled. For versions greater than 2.12.2 you can login with OAUTH.
11
12
12
13
> For more information on authenticating with SAML single sign-on, see "[About authentication with SAML single sign-on](https://help.github.com/articles/about-authentication-with-saml-single-sign-on)."
13
14
15
+
> For more information on creating personal access tokens, see "[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line). The required scopes for the personal access token are: `user`, `repo`, `gist`, and `write:public_key`.
16
+
17
+
14
18
1. In Visual Studio, select **Team Explorer** from the **View** menu.
15
19

16
20
2. In the Team Explorer pane, click the **Manage Connections** toolbar button.
@@ -19,12 +23,12 @@ Before you authenticate, you must already have a GitHub or GitHub Enterprise acc
19
23

20
24
4. In the **Connect to GitHub dialog** choose **GitHub** or **GitHub Enterprise**, depending on which product you're using.
21
25
22
-
-**GitHub option**:
23
-

24
-
- To sign in with credentials, enter either username or email and password.
25
-
- To sign in with SSO, select `Sign in with your browser`.
26
+
**GitHub option**:
27
+

28
+
- To sign in with credentials, enter either username or email and password.
29
+
- To sign in with SSO, select `Sign in with your browser`.
26
30
27
-
-**GitHub Enterprise option**:
28
-

29
-
- To sign in with credentials, first enter GitHub Enterprise server address. Once a valid server address is entered, a `Token` field appears and a valid token can be entered to sign in.
31
+
**GitHub Enterprise option**:
32
+

33
+
- To sign in with credentials, first enter GitHub Enterprise server address. Once a valid server address is entered, a `Token` field appears and a valid token can be entered to sign in.
30
34
- To sign in with SSO, first enter the GitHub Enterprise server address. Once a valid server address is entered, select `Sign in with your browser`. Follow the steps to authenticate with your SSO provider.
0 commit comments