Skip to content

Commit 1e2cfb2

Browse files
authored
fix typo + acrolinx (#23867)
1 parent f7be53e commit 1e2cfb2

File tree

1 file changed

+4
-4
lines changed
  • docs/architecture/microservices/secure-net-microservices-web-applications

1 file changed

+4
-4
lines changed

docs/architecture/microservices/secure-net-microservices-web-applications/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -124,13 +124,13 @@ In all cases, you must complete an application registration procedure that is ve
124124

125125
1. Getting a Client Application ID.
126126
2. Getting a Client Application Secret.
127-
3. Configuring an redirection URL, that's handled by the authorization middleware and the registered provider
127+
3. Configuring a redirection URL, that's handled by the authorization middleware and the registered provider
128128
4. Optionally, configuring a sign-out URL to properly handle sign out in a Single Sign On (SSO) scenario.
129129

130130
For details on configuring your app for an external provider, see the [External provider authentication in the ASP.NET Core documentation](/aspnet/core/security/authentication/social/)).
131131

132-
>[!TIP]
133-
>All details are handled by the authorization middleware and services previously mentioned. So, you just have to choose the **Individual User Account** authentication option when you create the ASP.NET Code web application project in Visual Studio, as shown in Figure 9-3, besides registering the authentication providers previously mentioned.
132+
> [!TIP]
133+
> All details are handled by the authorization middleware and services previously mentioned. So, you just have to choose the **Individual User Account** authentication option when you create the ASP.NET Core web application project in Visual Studio, as shown in Figure 9-3, besides registering the authentication providers previously mentioned.
134134
135135
![Screenshot of the New ASP.NET Core Web Application dialog.](./media/index/select-individual-user-account-authentication-option.png)
136136

@@ -201,7 +201,7 @@ public void ConfigureServices(IServiceCollection services)
201201
}
202202
```
203203

204-
Note that when you use this workflow, the ASP.NET Core Identity middleware is not needed, because all user information storage and authentication is handled by the Identity service.
204+
When you use this workflow, the ASP.NET Core Identity middleware is not needed, because all user information storage and authentication is handled by the Identity service.
205205

206206
### Issue security tokens from an ASP.NET Core service
207207

0 commit comments

Comments
 (0)