On the Configure Application Permissions screen, make sure openid is selected and click Next. On the Apply Access Control Policy screen, select Permit everyone and click Next.
This value will be used later in the application's App.config and Web.config files. On the Configure Web API screen, enter the Identifier: Click Add. Enter the following for Redirect URI: Click Add. It will be used later as the value for ClientId in the application's App.config file. Click Next.Ĭopy the Client Identifier value. On the Application Group Wizard, for the Name enter NativeAppToWebApi and under Client-Server applications select the Native application accessing a Web API template. In AD FS Management, right-click on Application Groups and select Add Application Group.
#Appdelete how to
This section shows how to register the Native App as a public client and Web API as a Relying Party (RP) in AD FS AD FS 2019 or later configured and running.To better understand how to configure a Native App in AD FS to acquire access token interactively, let's use a sample available here and walkthrough the app registration and code configuration steps. To enable this interaction, MSAL leverages a web browser. To call a Web API from a Native App that signs in users, you can use MSAL's AcquireTokenInteractive token acquisition method. In this flow you add authentication to your Native App (public client), which can therefore sign in users and calls a Web API. Learn how to build a native app signing-in users authenticated by AD FS 2019 and acquiring tokens using MSAL library to call web APIs.īefore reading this article, you should be familiar with the AD FS concepts and Authorization code grant flow Overview
Applies to: Windows Server 2022, Windows Server 2019, AD FS 2019 and later
0 kommentar(er)
