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

Merge pull request #2354 from aspnet/tdykstra-patch-1 

add note about placement of usegoogleauth
pull/2356/head
Rick Anderson 2016-12-08 09:05:16 -10:00 committed by GitHub
parent 624bf4f73e ae2cd22d57
commit 4e1ed75e60
2 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
aspnetcore/security/authentication/social/google-logins.md
View File

@ -81,7 +81,7 @@ This tutorial shows you how to enable your users to sign in with their Google+ a
## Storing Google ClientID and ClientSecret
Link sensitive settings like Google `ClientID` and `ClientSecret` to your application configuration by using the [Secret Manager tool](../../app-secrets.md) instead of storing them in your configuration file directly, as described in the [social login overview page](index.md).
Link sensitive settings like Google `ClientID` and `ClientSecret` to your application configuration by using the [Secret Manager tool](../../app-secrets.md) instead of storing them in your configuration file directly, as described in the [social authentication overview page](index.md).
* Open the JSON file downloaded in the last step. Note the `client_id` and `client_secret` values present in the JSON structure.
@ -115,6 +115,9 @@ app.UseGoogleAuthentication(new GoogleOptions()
});
```
> [!NOTE]
> Call `UseIdentity` before you call `UseGoogleAuthentication`. See the [social authentication overview page](index.md).
## Sign in with Google
Run your application and click **Log in**. An option to sign in with Google appears:

4
aspnetcore/security/authentication/social/index.md
View File

@ -81,7 +81,7 @@ As a best practice, it is not recommended to store the secrets in a configuratio
The **SecretManager** tool stores sensitive application settings in the user profile folder on the local machine. These settings are then seamlessly merged with settings from all other sources during application startup.
> [NOTE!]
> [!NOTE]
> Most login providers assign **Application Id** and **Application Secret** during the registration process. These values are effectively the *user name* and *password* your application uses to access their API, and constitute the "secrets" linked to your application configuration with the help of **Secret Manager** instead of storing them in configuration files directly.
Install the [Secret Manager tool](../../app-secrets.md) so that you can use it to store tokens assigned by each login provider below.
@ -96,7 +96,7 @@ Use the following pages to configure your application to use the respective prov
* [Microsoft](microsoft-logins.md) instructions
* [Other provider](other-logins.md) instructions
> [NOTE!]
> [!NOTE]
> Call `app.UseIdentity` (in `Configure`) before any other external providers.
## Optionally set password