For this post I am choosing the option that allows anyone that has a Azure AD Account or consumers account (Xbox, Skype, etc) access to the Api. Choose who can access your application.Enter a name, I typically choose the name of the application and ‘Api’.This application is used by your ASP.NET Core Web API to check the client’s authentication.īack in the Azure portal for your tenant, click on ‘App Registration’, and then click on ‘+ New Registration’ In this post, we are only going to create on the client to connect to our API. An example of a client could be a Windows desktop application, developer application (Visual Studio, Postman, etc.), or other Apis. The reason I said at least two is because you should create one client for each client you will consume/call your API. Now that we have an Azure Active Directory (AAD) tenant created, we will have to have register at least two applications within the portal, an application that represents the API we are protecting, and an application that will represent the client. Registering Applications with the Directory Once the directory is created, you will see a message similar to this. We won’t be doing that as part of this post. You can add a custom domain like later on in the process. The organization name is required and should be something that relates to your organization. In the search box, type Azure Active Directory and select itĮnter an Organization name.Creating the Azure Active Directory (AAD) Tenant However, if you are starting without the infrastructure, like I was, there are a couple of things to do. The code for this is ridiculously simple, as that was the intention. Getting Started with Microsoft Identity Platform If you need one, you can start with the Contacts application at this commit.
0 Comments
Leave a Reply. |