-
Notifications
You must be signed in to change notification settings - Fork 145
Open
Labels
Description
Describe the bug
To Reproduce
Currently, we run one command per secret, which is painful for developers who want to contribute to our project.
Support for social login providers
If you want to allow your users to login with their social accounts, e.g. Facebook, follow instructions below.
Facebook
1 - Follow this guide to generate AppID and AppSecret.
2 - Execute the following instructions from TodoList/TodoList.Web:
dotnet user-secrets set Authentication:Facebook:AppId <app-id>
dotnet user-secrets set Authentication:Facebook:AppSecret <app-secret>
Google
1 - Follow this guide to generate ClientID and ClientSecret.
2 - Execute the following instructions from TodoList/TodoList.Web:
dotnet user-secrets set Authentication:Google:ClientId <client-id>
dotnet user-secrets set Authentication:Google:ClientSecret <client-secret>
Microsoft
1 - Follow this guide to generate ClientID and ClientSecret.
2 - Execute the following instructions from TodoList/TodoList.Web:
dotnet user-secrets set Authentication:Microsoft:ClientId <client-id>
dotnet user-secrets set Authentication:Microsoft:ClientSecret <client-secret>
Twitter
1 - Follow this guide to generate App ID and AppSecret.
2 - Execute the following instructions from TodoList/TodoList.Web:
dotnet user-secrets set Authentication:Twitter:ConsumerKey <consumer-key>
dotnet user-secrets set Authentication:Twitter:ConsumerSecret <consumer-secret>
Expected behavior
The user should only deploy a JSON containing the required USER_SECRETS
Include SendGrid ApiKey to the new secrets.
Additional context
Create a default JSON, containing the keys needed, with their values set to an empty string.
Here are more information and a guide on how to implement that: https://docs.microsoft.com/en-us/aspnet/core/security/app-secrets?view=aspnetcore-3.1&tabs=windows.