daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Convert sample URLs from hyperlinks to code

pull/2090/head
01binary 2016-11-10 19:55:19 -08:00
parent e190299fa1
commit 758a5c7000
4 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
aspnetcore/security/authentication/facebook-logins.md
View File

@ -37,7 +37,7 @@ This tutorial shows you how to enable your users to log in with their Facebook a
![image](sociallogins/_static/FBOAuthSetup.png) ![image](sociallogins/_static/FBOAuthSetup.png)
* Enter your base URI with *signin-facebook* appended into the **Valid OAuth Redirect URIs** field. For example, https://localhost:44320/**signin-facebook**. * Enter your base URI with *signin-facebook* appended into the **Valid OAuth Redirect URIs** field. For example, `https://localhost:44320/signin-facebook`.
> [!NOTE] > [!NOTE]
> You don't need to configure **signin-facebook** as a route in your app. The ASP.NET Core team's implementation of the OAuth flow will create a temporary socket (called a *backchannel*) that listens at this route just for the duration of the OAuth flow. > You don't need to configure **signin-facebook** as a route in your app. The ASP.NET Core team's implementation of the OAuth flow will create a temporary socket (called a *backchannel*) that listens at this route just for the duration of the OAuth flow.

2
aspnetcore/security/authentication/google-logins.md
View File

@ -54,7 +54,7 @@ This tutorial shows you how to enable your users to login with their Google+ acc
* Because we are creating a Google+ project with just one feature (logins), we can enter the same **Name** for the OAuth 2.0 client ID as the one we used for the project. * Because we are creating a Google+ project with just one feature (logins), we can enter the same **Name** for the OAuth 2.0 client ID as the one we used for the project.
* Enter your current site URL with *signin-google* appended into the **Authorized redirect URIs** field. For example, https://localhost:44320/**signin-google**. * Enter your current site URL with *signin-google* appended into the **Authorized redirect URIs** field. For example, `https://localhost:44320/signin-google`.
> [!NOTE] > [!NOTE]
> You don't need to configure **signin-google** as a route in your app. The ASP.NET Core team's implementation of the OAuth flow will create a temporary socket (called a *backchannel*) that listens at this route just for the duration of the OAuth flow. > You don't need to configure **signin-google** as a route in your app. The ASP.NET Core team's implementation of the OAuth flow will create a temporary socket (called a *backchannel*) that listens at this route just for the duration of the OAuth flow.

6
aspnetcore/security/authentication/microsoft-logins.md
View File

@ -41,15 +41,15 @@ If you don't already have a Microsoft account, tap *[Create one!](https://signup
![image](sociallogins/_static/MicrosoftDevAppPlatform.png) ![image](sociallogins/_static/MicrosoftDevAppPlatform.png)
* In the new *Web* platform section, enter your current site URL with *signin-microsoft* appended into the **Redirect URIs** field. * In the new *Web* platform section, enter your current site URL with *signin-microsoft* appended into the **Redirect URIs** field. For example, `https://localhost:44320/signin-microsoft`:
* Don't forget to tap **Add Url** to ensure the Url was added:
![image](sociallogins/_static/MicrosoftRedirectUri.png) ![image](sociallogins/_static/MicrosoftRedirectUri.png)
> [!NOTE] > [!NOTE]
> You don't need to configure **signin-microsoft** as a route in your app. The ASP.NET Core team's implementation of the OAuth flow will create a temporary socket (called a *backchannel*) that listens at this route just for the duration of the OAuth flow. > You don't need to configure **signin-microsoft** as a route in your app. The ASP.NET Core team's implementation of the OAuth flow will create a temporary socket (called a *backchannel*) that listens at this route just for the duration of the OAuth flow.
* Don't forget to tap **Add Url** to ensure the Url was added.
* Tap **Save** to save changes. * Tap **Save** to save changes.
## Storing Microsoft ApplicationId and Secret ## Storing Microsoft ApplicationId and Secret

2
aspnetcore/security/authentication/twitter-logins.md
View File

@ -25,7 +25,7 @@ This tutorial shows you how to enable your users to [log in with their Twitter a
![image](sociallogins/_static/TwitterCreate.png) ![image](sociallogins/_static/TwitterCreate.png)
* Enter your current site URL with *signin-twitter* appended into the **Callback URL** field. For example, https://localhost:44320/**signin-twitter**. * Enter your current site URL with *signin-twitter* appended into the **Callback URL** field. For example, `https://localhost:44320/signin-twitter`.
> [!NOTE] > [!NOTE]
> You don't need to configure **signin-twitter** as a route in your app. The ASP.NET Core team's implementation of the OAuth flow will create a temporary socket (called a *backchannel*) that listens at this route just for the duration of the OAuth flow. > You don't need to configure **signin-twitter** as a route in your app. The ASP.NET Core team's implementation of the OAuth flow will create a temporary socket (called a *backchannel*) that listens at this route just for the duration of the OAuth flow.