![]() Open Visual Studio and select the TodoAppService.NET6 project. This will be referred to as the Web API Application ID. Note the Application (client) ID in the Essentials section as you'll need this value to configure the backend service later on. This will be referred to as the Web API Scope. You'll need the scope when configuring the client. Select Add scope to complete the scope addition. User consent description: Allow the app to access TodoApp on your behalf.User consent display name: Access TodoApp.Admin consent description: Allows the app to access TodoApp as the signed-in user.Admin consent display name: Access TodoApp.Under Manage, select Expose an API > Add a scope.įor Application ID URI, accept the default by selecting Save and continue. Supported account types: Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g.Name: enter a name for your application for example, TodoApp Quickstart.Under Manage, select App registrations > New registration. Search for and select Azure Active Directory. If you have access to multiple tenants, use the Directories + subscriptions filter in the top menu to switch to the tenant in which you want to register the application. Add authentication checking to the ASP.NET 6 backend project.įirst, register the web API in your Azure Active Directory tenant and add a scope by following these steps:.Register an application with Azure Active Directory.To enable Azure Active Directory authentication for your backend service, you need to: ![]() Any tutorial that shows you how to enable authentication for an ASP.NET 6 service will work with Azure Mobile Apps. Your backend service is a standard ASP.NET 6 service. Add authentication to your backend service Although we use Azure Active Directory for authentication, you can use any authentication library you wish with Azure Mobile Apps. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |