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/remote-authentication/remote-authentication.md
+24Lines changed: 24 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,15 @@ There are just a few small code changes needed to enable remote authentication i
8
8
9
9
### ASP.NET app configuration
10
10
11
+
<<<<<<< HEAD
12
+
First, the ASP.NET app needs to be configured to add the authentication endpoint. This is done by calling the `AddRemoteAppServer` extension method on the `ISystemWebAdapterBuilder`:
First, theASP.NETappneedstobeconfiguredtoaddtheauthenticationendpoint. Thisisdonebycallingthe `AddRemoteApp` extensionmethodonthe `ISystemWebAdapterBuilder` toconfigurereceivingremotecalls, andbycalling `AddRemoteAuthentication` tosetuptheHTTPmodulethatwillwatchfor requests to the authentication endpoint. Note that remote authentication scenarios typically want to add proxy support, as well, so that any auth-related redirects will correctly route to the ASP.NET Core app rather than the ASP.NET one.
In the options configuration method passed to the `AddRemoteApp` call, you must specify an API key which is used to secure the endpoint so that only trusted callers can make requests to it (this same API key will be provided to the ASP.NET Core app when it is configured).
24
34
25
35
### ASP.NET Core app configuration
26
36
37
+
<<<<<<< HEAD
38
+
Next, the ASP.NET Core app needs to be configured to enable the authentication handler that will authenticate users by making an HTTP request to the ASP.NET app. This is done by calling `AddRemoteAppClient` when registering System.Web adapters services:
0 commit comments