Delegated permissions are appropriate for client apps that access a web API as the signed-in user, and whose access should be restricted to the permissions you select in the next step. Select the web API you registered as part of the prerequisites.ĭelegated permissions is selected by default. Select API permissions > Add a permission > My APIs. Select Azure Active Directory > App registrations, and then select your client application ( not your web API). In the top menu to select the tenant containing your client app's registration. If you have access to multiple tenants, use the Directories + subscriptions filter Once you've registered both your client app and web API and you've exposed the API by creating scopes, you can configure the client's permissions to the API by following these steps: In this section, you add permissions to the client app's registration. This diagram shows how the two app registrations relate to one another. If you don't yet have both a client app and a web API registered, complete the steps in the two Prerequisites articles. In the first scenario, you grant a client app access to your own web API, both of which you should have registered as part of the prerequisites. Completion of Quickstart: Configure an application to expose a web API.Completion of Quickstart: Register an application.An Azure account with an active subscription - create an account for free.Within its code, the web API can then provide permission-based access to its resources based on the scopes found in the access token.
You also provide the client app access to Microsoft Graph.īy specifying a web API's scopes in your client app's registration, the client app can obtain an access token containing those scopes from the Microsoft identity platform.
In this quickstart, you provide a client app registered with the Microsoft identity platform with scoped, permissions-based access to your own web API.
0 kommentar(er)
