![]() ![]() It is also important to check the boxes beside “Access tokens (used for implicit flows)” and “ID token (used for implicit and hybrid flows)”.ĭon’t forget to hit “Save” at the top after you have configured everything.Ĭongratulations, you have successfully created your API. Make sure to come back and add the entries then. Some of that information you only get when you created the API, which we will do later in this blog post. In those URL’s you have to replace “” with the port your API is using locally and “” with the URL you create when you create your API in azure.As redirect URL’s we don’t really need any but to be able to test our API locally, from Azure and via Postman we have to add the following entries. Under authentication, we have to add a platform (using the Add a platform button) of type “Web”. For this App Registration, we have several things to do. Let’s take a look at the specific configuration for the Web API App Registration. The following two chapters will describe the specific configuration needed for the two App Registrations. App RegistrationsĪs mentioned we do need two different App Registrations. Let’s come to the fun part and set up/implement our solution. One is used by the WebAPI to authenticate against Azure AD and the second is used by the custom connector to authenticate against the WebAPI. What we need are two App Registrations configured in a certain way. In the end, I came to a solution using another tutorial called “ Create a custom connector for a web API” as well as a lot of trial and error. It does cover parts of the solution but not quite those needed for a custom API hosted in Azure. SolutionĪt first, I followed a tutorial from Microsoft called “ Use Azure Active Directory with a custom connector in Power Automate“, which I found very confusing. Problems arose when authentication through AAD was introduced. The base of the custom connector was built rather easy and fast. Since citizen devs should be able to implement other flows against the same system in the future as well we thought a custom connector would be the best approach. We figured the easiest way would be to have a Power Automate Flow which triggers on certain conditions and creates rows in the System in question accordingly. ![]() We build a Mode-Driven App for the customer which should fetch and send data to the mentioned onPrem System through the API. net Core 5.0 and uses Azure Active Directory (AAD) for authentication. The customer does have a custom API that makes data from an internal (onPrem) system available and makes it possible to create new records within the system using a REST API. Let’s look a bit deeper into the given scenario. Custom Connector Test – Custom Connector. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |