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: 3.-Web-api-call-Microsoft-graph-for-personal-accounts/README-incremental-instructions.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,12 +91,12 @@ If you want to use this automation:
91
91
> Other ways of running the scripts are described in [App Creation Scripts](./AppCreationScripts/AppCreationScripts.md)
92
92
93
93
1. Once you've run the script, be sure to follow the manual steps. Indeed Azure AD PowerShell does not yet provide full control on applications consuming v2.0 tokens, even if this registration is already possible from the Azure portal:
94
-
1. In the list of pages for the application registration of the *TodoListService-v2* application, select **Manifest**
94
+
1. In the list of pages for the application registration of the *TodoListClient-and-Service* application, select **Manifest**
95
95
- in the manifest, search for **"accessTokenAcceptedVersion"**, and replace **null** by **2**. This property lets Azure AD know that the Web API accepts v2.0 tokens
96
96
- search for **signInAudience** and make sure it's set to **AzureADandPersonalMicrosoftAccount**
97
97
- Select **Save**
98
-
1. In the **Authentication** page for the *TodoListService-v2* application, check the `urn:ietf:wg:oauth:2.0:oob` reply URI so that the client can propose incremental consent to the user for the Web API when needed.
99
-
1. In tthe application registration page for the *TodoListClient-v2* application, select the **Manifest** section:
98
+
1. In the **Authentication** page for the *TodoListClient-and-Service* application, check the `urn:ietf:wg:oauth:2.0:oob` reply URI so that the client can propose incremental consent to the user for the Web API when needed.
99
+
1. In tthe application registration page for the *TodoListClient-and-Service* application, select the **Manifest** section:
100
100
- search for **signInAudience** and make sure it's set to **AzureADandPersonalMicrosoftAccount**
101
101
- Select **Save**
102
102
@@ -127,7 +127,7 @@ These instructions only show the differences with the first part.
127
127
- Select the **Add permissions** button
128
128
-[Optional] if you are a tenant admin, and agree to grant the admin consent to the web api, select **Grant admin consent for {your tenant domain}**.
129
129
1.[Otherwise] If you have not granted admin consent to the Web API in the previous optional step, select **Authentication** in the list of pages and there:
130
-
- Check the `urn:ietf:wg:oauth:2.0:oob` Redirect URI checkbox. This is so that the client can propose incremental consent to the user for the downstream web apis used by our *TodoListService-v2* Web API.
130
+
- Check the `urn:ietf:wg:oauth:2.0:oob` Redirect URI checkbox. This is so that the client can propose incremental consent to the user for the downstream web apis used by our *TodoListService* Web API.
131
131
- Select **Save**
132
132
1.[Optional] Select the **Manifest** section and:
133
133
- in the manifest, search for **"accessTokenAcceptedVersion"**, and see that its value is **2**. This property lets Azure AD know that the Web API accepts v2.0 tokens
@@ -147,8 +147,8 @@ This constrain is ensured by `ida:Tenant` in `TodoListClient\App.Config` having
147
147
#### Configure the TodoListService C# project
148
148
149
149
1. Open the solution in Visual Studio.
150
-
1. In the *TodoListService-v2* project, open the `appsettings.json` file.
151
-
1. Find the `ClientSecret` property and replace the existing value with the key you saved during the creation of the `TodoListService-v2` app, in the Azure portal.
150
+
1. In the *TodoListClient-and-Service* project, open the `appsettings.json` file.
151
+
1. Find the `ClientSecret` property and replace the existing value with the key you saved during the creation of the `TodoListClient-and-Service` app, in the Azure portal.
Copy file name to clipboardExpand all lines: 3.-Web-api-call-Microsoft-graph-for-personal-accounts/README.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -113,7 +113,7 @@ If you want to use this automation:
113
113
```
114
114
> Other ways of running the scripts are described in [App Creation Scripts](./AppCreationScripts/AppCreationScripts.md)
115
115
116
-
1. In the list of pages for the application registration of the `TodoListService-v2` application, select **Manifest**
116
+
1. In the list of pages for the application registration of the `TodoListClient-and-Service` application, select **Manifest**
117
117
- in the manifest, search for **"accessTokenAcceptedVersion"**, and replace **null** by **2**. This property lets Azure AD know that the Web API accepts v2.0 tokens
118
118
- Select **Save**
119
119
@@ -194,9 +194,9 @@ Accepted tenants can have the following values:
194
194
Note: if you used the setup scripts, the changes below will have been applied for you
195
195
196
196
1. Open the solution in Visual Studio.
197
-
1. In the *TodoListService-v2* project, open the `appsettings.json` file.
198
-
1. Find the `ClientId` property and replace the value with the Application ID (Client ID) property of the *TodoListService-v2* application, that you registered earlier.
199
-
1. Find the `ClientSecret` property and replace the existing value with the key you saved during the creation of the `TodoListService-v2` app, in the Azure portal.
197
+
1. In the *TodoListService* project, open the `appsettings.json` file.
198
+
1. Find the `ClientId` property and replace the value with the Application ID (Client ID) property of the *TodoListClient-and-Service* application, that you registered earlier.
199
+
1. Find the `ClientSecret` property and replace the existing value with the key you saved during the creation of the `TodoListClient-and-Service` app, in the Azure portal.
200
200
1.[Optional] if you want to limit sign-in to users in your organization, also update the following properties:
201
201
-`Domain`, replacing the existing value with your AAD tenant domain, for example, contoso.onmicrosoft.com.
202
202
-`TenantId`, replacing the existing value with the Tenant ID.
@@ -205,9 +205,9 @@ Note: if you used the setup scripts, the changes below will have been applied fo
205
205
206
206
Note: if you used the setup scripts, the changes below will have been applied for you
207
207
208
-
1. In the TodoListClient project, open `App.config`.
209
-
1. Find the app key `ida:ClientId` and replace the value with the ApplicationID (Client ID) for the *TodoListClient-v2* app copied from the app registration page.
210
-
1. Find the app key `todo:TodoListScope` and replace the value with the scope of the TodoListService-v2 application copied from the app registration in the **Expose an API** tab, but replace the scope by `.default` (of the form ``api://<Application ID of service>/.default`` if you followed the instructions above)
208
+
1. In the *TodoListClient* project, open `App.config`.
209
+
1. Find the app key `ida:ClientId` and replace the value with the ApplicationID (Client ID) for the *TodoListClient-and-Service* app copied from the app registration page.
210
+
1. Find the app key `todo:TodoListScope` and replace the value with the scope of the TodoListClient-and-Service application copied from the app registration in the **Expose an API** tab, but replace the scope by `.default` (of the form ``api://<Application ID of service>/.default`` if you followed the instructions above)
211
211
1.[Optional] If you want your application to work only in your organization (only in your tenant) you'll also need to Find the app key `ida:Tenant` and replace the value with your AAD Tenant ID (GUID). Alternatively you can also use your AAD tenant Name (for example, contoso.onmicrosoft.com)
212
212
1.[Optional] If you changed the default URL for your service application, find the app key `todo:TodoListBaseAddress` and replace the value with the base address of the TodoListService project.
213
213
@@ -224,7 +224,7 @@ This behavior is expected as you are not authenticated. The WPF application will
224
224
225
225
Explore the sample by signing in into the TodoList client, adding items to the To Do list, removing the user account (clearing the cache), and starting again. As explained, if you stop the application without removing the user account, the next time you run the application, you won't be prompted to sign in again. That is because the sample implements a persistent cache for MSAL, and remembers the tokens from the previous run.
226
226
227
-
NOTE: Remember, the To-Do list is stored in memory in this `TodoListService-v2` sample. Each time you run the TodoListService API, your To-Do list will get emptied.
227
+
NOTE: Remember, the To-Do list is stored in memory in this *TodoListService* sample. Each time you run the TodoListService API, your To-Do list will get emptied.
0 commit comments