Image for post
Image for post

Note: this is part 2 of a series of articles related to security in Blazor WebAssembly applications:
Part 1: Securing Blazor WebAssembly with Identity Server 4
Part 2: Role-based security with Blazor and Identity Server 4 (this article)

In a previous article we’ve introduced how authentication works in Blazor WebAssembly and we’ve seen a simple example on how to create a Blazor client, implement the login flow via Identity Server 4 and retrieve an access token to call a protected Web API.

Image for post
Image for post

However, every real-world application will sooner or later need to deal with user roles, in order to offer different functionalities to its users depending on what they have access to. …


Image for post
Image for post

Note: this is part 1 of a series of articles related to security in Blazor WebAssembly applications:
Part 1: Securing Blazor WebAssembly with Identity Server 4 (this article)
Part 2: Role-based security with Blazor and Identity Server 4

The new Blazor WebAssembly 3.2.0


Image for post
Image for post

Last Friday I spent some time investigating an annoying bug we had in production: we have a relatively standard Single Page Web Application, in which a ASP.NET Core 2.2 Web API serves a React.js front-end. The Web API is runs on Azure App Service, using the InProcess hosting mode.

The issue: from time to time, the API would hang and start raising an HTTP 500.30 status code on any endpoint.

Image for post
Image for post

When that happened, either a restart or the proactive auto-healing of Azure App Service would eventually fix the issue and restore the functionality. …

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store