Tracher backchannel note fix
parent
ebb16155eb
commit
e8a9e6d236
|
@ -42,7 +42,7 @@ This tutorial shows you how to enable your users to log in with their Facebook a
|
|||
* When deploying the site you'll need to register a new public url.
|
||||
|
||||
> [!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 Facebook middleware will automatically intercept requests at this route and handle them to implement the OAuth flow.
|
||||
|
||||
* Make a note of your *App ID* and your *App Secret* before dismissing this page so that you can add both into your ASP.NET Core app later in this tutorial.
|
||||
|
||||
|
|
|
@ -59,7 +59,7 @@ This tutorial shows you how to enable your users to login with their Google+ acc
|
|||
* When deploying the site you'll need to register a new public url.
|
||||
|
||||
> [!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 Google middleware will automatically intercept requests at this route and handle them to implement the OAuth flow.
|
||||
|
||||
* Tap **Create client ID**, which will take you to the third step:
|
||||
|
||||
|
|
|
@ -48,7 +48,7 @@ If you don't already have a Microsoft account, tap *[Create one!](https://signup
|
|||
* When deploying the site you'll need to register a new public url.
|
||||
|
||||
> [!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 Microsoft Account middleware will automatically intercept requests at this route and handle them to implement the OAuth flow.
|
||||
|
||||
* Don't forget to tap **Add Url** to ensure the Url was added.
|
||||
|
||||
|
|
|
@ -30,7 +30,7 @@ This tutorial shows you how to enable your users to [log in with their Twitter a
|
|||
* When deploying the site you'll need to register a new public url.
|
||||
|
||||
> [!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 Twitter middleware will automatically intercept requests at this route and handle them to implement the OAuth flow.
|
||||
|
||||
* Tap **Create your Twitter application**. New application details will be displayed:
|
||||
|
||||
|
|
Loading…
Reference in New Issue