You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/architecture/microservices/secure-net-microservices-web-applications/index.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -124,13 +124,13 @@ In all cases, you must complete an application registration procedure that is ve
124
124
125
125
1. Getting a Client Application ID.
126
126
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
128
128
4. Optionally, configuring a sign-out URL to properly handle sign out in a Single Sign On (SSO) scenario.
129
129
130
130
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/)).
131
131
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.
134
134
135
135

136
136
@@ -201,7 +201,7 @@ public void ConfigureServices(IServiceCollection services)
201
201
}
202
202
```
203
203
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.
205
205
206
206
### Issue security tokens from an ASP.NET Core service
0 commit comments