What I Learned:Blazor Auth with Server Side Pre-Rendering

March 22, 2024

•

3 Minute Read

As I’ve mentioned, I’ve been working a lot with Blazor at work and one of the issues I ran into was supporting authentication and user sessions while still supporting server side pre-rendering on certain pages.

When handling the user session, I would be putting the session key into session storage using Microsoft’s protected session store library. This would require using JavaScript which isn’t available during initialization on pre-rendered pages and components.

After batting my head around this for a while, I stumbled upon a Stack Overflow post that gave me my solution, albeit, not the greatest one, but one that so far seems to be working well enough.

Let’s look back at my old post about custom auth in Blazor. More specifically the GetAuthenticationStateAsync method.

CustomAuthenticationStateProvider.cs

public override async Task<AuthenticationState> GetAuthenticationStateAsync()
{
	var identity = new ClaimsIdentity();
	
	var userId = await _sessionStorageService.GetItemAsync<int>("userId");
	
	if (userId > 0)
	{
		var user = await _userManager.FindByIdAsync(userId.ToString());
		
		if (user is not null)
		{
			identity = new ClaimsIdentity(new[]
			{
				new Claim("UserAccountId", user.Id.ToString()),
				new Claim(ClaimTypes.Email, user.Email ?? ""),
				new Claim(ClaimTypes.Name, user.Name)
			}, "CardOrgAuth");
		}
		else
		{
			// can't find the user, kill the session
			await _sessionStorageService.RemoveItemAsync("userId");
		}
	}
	
	return await Task.FromResult(new AuthenticationState(new ClaimsPrincipal(identity)));
}

The issue I ran into was on the line where I would pull the user ID from session storage.

var userId = await _sessionStorageService.GetItemAsync<int>("userId");

This would require Blazor executing JavaScript which isn’t available, so the page would crash. The solution or workaround for this, while not elegant, is to wrap the check in a try-catch statement.

CustomAuthenticationStateProvider.cs

public override async Task<AuthenticationState> GetAuthenticationStateAsync()
{
	var identity = new ClaimsIdentity();

	try
	{
		var userId = await _sessionStorageService.GetItemAsync<int>("userId");

		if (userId > 0)
		{
			var user = await _userManager.FindByIdAsync(userId.ToString());

			if (user is not null)
			{
				identity = new ClaimsIdentity(new[]
				{
					new Claim("UserAccountId", user.Id.ToString()),
					new Claim(ClaimTypes.Email, user.Email ?? ""),
					new Claim(ClaimTypes.Name, user.Name)
				}, "CardOrgAuth");
			}
			else
			{
				// can't find the user, kill the session
				await _sessionStorageService.RemoveItemAsync("userId");
			}
		}
	}
	catch { }

	return await Task.FromResult(new AuthenticationState(new ClaimsPrincipal(identity)));
}

The next step is to go into the layout and add the following code.

MainLayout.razor

@inject AuthenticationStateProvider AuthStateProvider

<html>
	...
</html>

@code {
	protected override async Task OnAfterRenderAsync(bool firstRender)
	{
    	await ((CustomAuthenticationStateProvider)AuthStateProvider).GetAuthenticationStateAsync();
	}
}

In the OnAfterRenderAsync lifecycle method, JavaScript can be utilized, so the user session can be fetched and the pages, even those with pre-rendering turned on will load correctly.

It might not be the most elegant solution or even one that is preferred, but it has been working for me so far.

Reply via: Email • Mastodon • Bluesky