Skip to main content
  1. Tags/

Dotnet

Front Door incomplete first request

·2 mins

Yesterday I was working with one of our customers to fix an issue with an ASP.NET application throwing an error. That application threw the error on the first request coming in through Azure Front Door. When we sent a request to the original (back end) URL, the application worked fine and never threw the exception. 🤔

Video content 📹

·1 min

Some time ago Oscar van Tol and I started creating video content for the community. We call them #Betatalks and create them because of two very important reasons:

  1. We believe in sharing knowledge
  2. It’s. So. Much. Fun. 🤣

We talk about a lot of developer stuff: from “Microsoft Build 2019 Highlights” in episode 1 to “C# 8, What’s new?” in episode 4.

Managed Identity – Part I

This post is part of a series on Managed Identity. Stay tuned for future posts.

Introduction #

Connecting your application to a resource like Storage or a SQL database used to involve a connection string. This isn’t very secure. These settings are available through the Azure portal. So they might get compromised.
With the introduction of Azure Key Vault, we got a way of separating these secrets from our application configuration. We can store them in a safe, secure place. There’s only one downside: you need a connection string to connect to Key Vault. So the problem isn’t solved; we only moved it. We can still get to the connection string the application uses to get secrets from Key Vault. So anyone with access to that connection string can still access those same secrets.