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: 7-AdvancedScenarios/1-call-api-obo/README.md
+9-12Lines changed: 9 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ or download and extract the repository .zip file.
57
57
58
58
```console
59
59
cd ms-identity-javascript-angular-tutorial
60
-
cd 3-Authorization-II/1-call-api/API/TodoListAPI
60
+
cd 7-AdvancedScenarios/1-call-api-obo/API
61
61
dotnet restore
62
62
```
63
63
@@ -201,28 +201,25 @@ Open the project in your IDE (like Visual Studio or Visual Studio Code) to confi
201
201
202
202
> In the steps below, "ClientID" is the same as "Application ID" or "AppId".
203
203
204
-
1. Open the `SPA\src\app\authConfig.ts` file.
204
+
1. Open the `SPA\src\app\auth-config.ts` file.
205
205
1. Find the key `Enter_the_Application_Id_Here` and replace the existing value with the application ID (clientId) of `ProfileSPA` app copied from the Azure portal.
206
206
1. Find the key `Enter_the_Tenant_Info_Here` and replace the existing value with your Azure AD tenant ID.
207
207
1. Find the key `Enter_the_Application_Id_of_Service_Here` and replace the existing value with the application ID (clientId) of `ProfileAPI` app copied from the Azure portal.
208
208
209
209
#### Configure Known Client Applications for service (ProfileAPI)
210
210
211
-
For a middle tier Web API (`ProfileAPI`) to be able to call a downstream Web API, the middle tier app needs to be granted the required permissions as well.
212
-
However, since the middle tier cannot interact with the signed-in user, it needs to be explicitly bound to the client app in its **Azure AD** registration.
213
-
This binding merges the permissions required by both the client and the middle tier Web Api and presents it to the end user in a single consent dialog. The user then consent to this combined set of permissions.
211
+
For a middle-tier Web API (`ProfileAPI`) to be able to call a downstream web API, the middle-tier app needs to be granted the required permissions as well. However, since the middle-tier cannot interact with the signed-in user, it needs to be explicitly bound to the client app in its **Azure AD** registration. This binding merges the permissions required by both the client and the middle tier Web Api and presents it to the end user in a single consent dialog. The user then consent to this combined set of permissions.
214
212
215
-
To achieve this, you need to add the **Application Id** of the client app, in the Manifest of the Web API in the `knownClientApplications` property. Here's how:
213
+
To achieve this, you need to add the **Application Id** of the client app, in the Manifest of the web API in the `knownClientApplications` property. Here's how:
216
214
217
215
1. In the [Azure portal](https://portal.azure.com), navigate to your `ProfileAPI` app registration, and select **Manifest** section.
218
-
1. In the manifest editor, change the `"knownClientApplications": []` line so that the array contains
219
-
the Client ID of the client application (`ProfileSPA`) as an element of the array.
216
+
1. In the manifest editor, change the `"knownClientApplications": []` line so that the array contains the Client ID of the client application (`ProfileSPA`) as an element of the array.
0 commit comments