Skip to main content

Azure Static Web App–Authorization

As a follow-up on the presentation I did at CloudBrew about Azure Static Web Apps I want to write a series of blog posts.

If we talk about authentication, we also have to talk about authorization. Authorization is role based and every user gets at least one role for free: the “anonymous” role. Once you are authenticated, a second role is assigned; the “authenticated” role.

You can see this by browsing to the .auth/me endpoint after authenticating. You’ll get a response back similar to this:

Roles can be assigned to specific routes in the staticwebapps.json.config file:

Remark: Roles are matched on an OR basis. If a user is in any of the listed roles, then access is granted.

Custom roles

These 2 roles are sufficient to get you started but sooner or later you want to assign custom roles. This can be done either through invitations or through an Azure Function(which I’ll show in the next post).

Invitations can be configured and sent from the Azure Portal, using provider-specific email addresses for the user.  You get an invite link that can be send to potential users. Users can click on the invite link to login with that custom role assigned automatically.

  • Go to your Static Web App in the Azure portal.
  • Click on Role Management.

  • Click on the Invite button.
  • Now we need to enter a few details
    • The built-in Authentication provider we want to use (Github or Azure AD)
    • The email address of the user
    • The domain name of the Static Web App
    • The custom role we ant to assign
    • The invitation expiration time(in hours)

  • After filling in all the details, click on Generate to generate a link.

Once users click on this link, the role is assigned as you can see in the portal:

And when calling the .auth/me endpoint:

More information

Configure Azure Static Web Apps | Microsoft Learn

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...