From eef4000a0397f5ce14c07aaf3d6a668af91597bc Mon Sep 17 00:00:00 2001 From: Enis Necipoglu Date: Fri, 20 May 2022 09:27:45 +0300 Subject: [PATCH] Move Blazor Security document section to wasm --- docs/en/UI/Blazor/Authentication.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/en/UI/Blazor/Authentication.md b/docs/en/UI/Blazor/Authentication.md index 45aafabaf3..eb39e05c6b 100644 --- a/docs/en/UI/Blazor/Authentication.md +++ b/docs/en/UI/Blazor/Authentication.md @@ -21,6 +21,8 @@ The Blazor Server application UI is actually a hybrid application that is combin * 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. -{{end}} -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 + +See the [Blazor Security document](https://docs.microsoft.com/en-us/aspnet/core/blazor/security) to understand and customize the authentication process. + +{{end}} \ No newline at end of file