Andrew Wilson's Blog

{ ... Plan - Architect - Develop - Reflect - Improve - Repeat ... }

Easy Auth | Standard Logic App with Azure API Management

Overview The recent work that I have been doing with Standard Logic Apps and linking them as backends to Azure API Management has relied on the use of the Logic App Workflow SAS key for security. This is a valid authentication approach, but there are risks that you need to be aware of as well as best practices that you need to be abiding by. Such as: Some Potential Risks:

Posted by Andrew Wilson on Friday, February 16, 2024

Azure API Management | Logic App (Standard) Backend Using a Swagger Definition

Overview After setting up a Logic App (Standard) Backend in Azure API Management (APIM) in my last post, I wanted to try and see if I could create a Swagger definition from a Standard Logic App which could then be used to simplify the API authoring process in APIM. This post shows my methods of doing so. If you haven’t already I would recommend reading my previous post as this one will be working off of the building blocks of the last.

Posted by Andrew Wilson on Thursday, February 1, 2024

Azure API Management | Logic App (Standard) Backend

Overview Updated [31/01/2024]: See New Post showing methods of linking a Logic App Standard as a Backend to APIM through a Swagger Definition. I have recently been reviewing the method in which a Logic App (Standard) workflow would be setup as an API in API Management. My aim is to overcome and simplify the limitation whereby directly importing a Logic App (Standard) workflow is not available, only in consumption. After some exploration I believe I have identified a configurable and secure method in setting up the front-to-backend routing as can be seen in the diagram below: The overall design aims to abstract the backend from the api operations, i.

Posted by Andrew Wilson on Tuesday, January 2, 2024

Azure API Management | Unintentional Pass through of Subscription Key Header

Problem Space There is a potential unintentional side effect when you add a APIM subscription key as a header to an inbound request. The header is not stripped from the request prior to being sent to the configured backend service. Rather it is retained. If you manage the backing service and are not concerned with the disclosure of the subscription key, then no problem. However, being overly permissive of this information may make your API more vulnerable to security threats and disallows a separation of concerns.

Posted by Andrew Wilson on Tuesday, November 21, 2023

Azure API Management | Product Required Subscription Behaviours

Background | Functional Workings of APIM Subscriptions Subscriptions are a nice and easy method of securing your APIs in APIM, however as I bumped into a small detail around their use the other day, I thought it wise to note it down. Azure API Management Subscriptions operate at three scope levels: All APIs Applies to any API that requires a Subscription. As this will allow access to ANY api, use this with caution.

Posted by Andrew Wilson on Tuesday, December 20, 2022

avatar

Andrew Wilson
Husband - Father - Principal Consultant at Black Marble.

Has a passion for creating software [especially solution integrations] that help others execute their jobs faster and more efficiently.

QUICK LINKS
FEATURED TAGS
api-management apim apim-policy arm azure azure-devops azure-portal bicep biztalk biztalk-deployment-framework btdf dsc fluent-ui git keyvault logic-app logic-app-standard nerd-fonts office-ui-fabric ohmyposh powershell rbac react roles sso storage-account strong-name-key swagger typescript vs-code windows-terminal winget winget-configuration yaml-pipeline