From 3dfbe463861bd3df7668f74ee7238569d66bd77c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Halil=20=C4=B0brahim=20Kalkan?= Date: Mon, 7 Dec 2020 18:53:16 +0300 Subject: [PATCH] Document Blazor UI: Authentication --- docs/en/UI/Blazor/Authentication.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/en/UI/Blazor/Authentication.md b/docs/en/UI/Blazor/Authentication.md index 6c1cdb31f5..9dc34ebce5 100644 --- a/docs/en/UI/Blazor/Authentication.md +++ b/docs/en/UI/Blazor/Authentication.md @@ -1,3 +1,11 @@ # Blazor UI: Authentication -TODO \ No newline at end of file +The [application startup template](../../Startup-Templates/Application.md) is properly configured to use OpenId Connect to authenticate the user through the server side login form; + +* When the Blazor application needs to authenticate, it is redirected to the server side. +* Users can enter username & password to login if they already have an account. If not, they can use the register form to create a new user. They can also use forgot password and other features. The server side uses IdentityServer4 to handle the authentication. +* Finally, they are redirected back to the Blazor application to complete the login process. + +This is a typical and recommended approach to implement authentication in Single-Page Applications. The client side configuration is done in the startup template, so you can change it. + +See the [Blazor Security document](https://docs.microsoft.com/en-us/aspnet/core/blazor/security) to understand and customize the authentication process. \ No newline at end of file