Skip to content
This repository was archived by the owner on Jun 21, 2023. It is now read-only.

Commit 22d167b

Browse files
Merge branch 'master' into enhancements/add-user-guid-to-metrics
2 parents 2decd0e + 30b5ad0 commit 22d167b

File tree

3 files changed

+16
-2
lines changed

3 files changed

+16
-2
lines changed

docs/getting-started/authenticating-to-github.md

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,12 @@ Before you authenticate, you must already have a GitHub or GitHub Enterprise acc
77
- 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/)".
88
- For a GitHub Enterprise account, contact your GitHub Enterprise site administrator.
99

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. 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). 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)."
10+
> **Note:** If your organization is on the [Business plan](https://help.github.com/articles/organization-billing-plans) and has not enabled SAML single sign-on or login with username and passowrd, you must create and authorize a personal access token to access protected content. In addition, SAML single sign-on is not available for GitHub enterprise versions less than 2.12.2.
11+
12+
> 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+
> 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`.
15+
1116

1217
1. In Visual Studio, select **Team Explorer** from the **View** menu.
1318
![Team Explorer in the view menu](images/view_team_explorer.png)
@@ -16,4 +21,13 @@ Before you authenticate, you must already have a GitHub or GitHub Enterprise acc
1621
3. Click the **Connect** link in the GitHub section. If you are already connected to a GitHub instance and want to connect to another, this link will not be visible; instead click **Manage Connections** and then **Connect to GitHub**.
1722
![Connect to GitHub in the manage connections dropdown in the Team Explorer pane](images/connect_to_github.png)
1823
4. In the **Connect to GitHub dialog** choose **GitHub** or **GitHub Enterprise**, depending on which product you're using.
19-
5. Type your credentials, then click **Sign In**.
24+
25+
**GitHub option**:
26+
![Connect to GitHub dialog view](images/connect-to-github-dialog.png)
27+
- To sign in with credentials, enter either username or email and password.
28+
- To sign in with SSO, select `Sign in with your browser`.
29+
30+
**GitHub Enterprise option**:
31+
![Connect to GitHub Enterprise dialog view](images/connect-to-github-enterprise-dialog.png)
32+
- 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.
33+
- 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.
41 KB
Loading
36.9 KB
Loading

0 commit comments

Comments
 (0)