From f29ebcab956a368f7089c389cdf169c54c979fca Mon Sep 17 00:00:00 2001 From: "MisterMik [MSFT]" <15340423+mistermik@users.noreply.github.com> Date: Thu, 16 Feb 2023 16:27:43 -0800 Subject: [PATCH] Update Custom-Id-Tokens-in-AD-FS.md Without adding the client identifier in the WebAPI the customized token will never be emitted. This is a key step in the configuration which is missing. I spent a few hours to figure this out. --- .../identity/ad-fs/development/Custom-Id-Tokens-in-AD-FS.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/WindowsServerDocs/identity/ad-fs/development/Custom-Id-Tokens-in-AD-FS.md b/WindowsServerDocs/identity/ad-fs/development/Custom-Id-Tokens-in-AD-FS.md index b3fd48caaf..f1749b6abd 100644 --- a/WindowsServerDocs/identity/ad-fs/development/Custom-Id-Tokens-in-AD-FS.md +++ b/WindowsServerDocs/identity/ad-fs/development/Custom-Id-Tokens-in-AD-FS.md @@ -60,7 +60,9 @@ Follow the steps below to create and configure the application in AD FS for rece ![Screenshot of the Native application page of the Add Application Group Wizard showing the redirect U R I .](media/Custom-Id-Tokens-in-AD-FS/clientsnap2.png) -5. On the **Configure Web API** screen, enter the following for **Identifier** - **https://contoso.com/WebApp**. Click **Add**. Click **Next**. This value will be used later for **ida:ResourceID** in the applications web.config file. +5. On the **Configure Web API** screen, enter the followings for **Identifier**: + - **https://contoso.com/WebApp**. Click **Add**. This value will be used later for **ida:ResourceID** in the applications web.config file. + - Enter the **Client Identifier** value from Step 3 as **Identifier** (e.g. 7ac3c470-1ecd-43d9-b444-42b34fb21028) and Click **Add**. Click **Next** ![Screenshot of the Configure Web API page of the Add Application Group Wizard showing the correct identifier.](media/Custom-Id-Tokens-in-AD-FS/clientsnap3.png)