Services
Technology Web App Development Mobile App Development Windows App Development Database Development UI/UX Development Cloud Development SEO Digital Marketing Guest Posting Content Writing Artificial Intelligence Data Science ERP Development CRM Development CMS Development LMS Development Business Listing Blockchain Technology Startup Promotion AI Tools Integration
Products
Data Converter Cleaner TUC - Unit Converter Import Export Survey Manager Tweet Controller
Developer
Article Blog Forum Interview Beginner News Startup Quiz
Users
Career
Apply Job Internship
Pricing
Login Sign Up Get a Quote

forum

Home Forums How to configure Hangfire with SQL Server and dashboard authorization in ASP.NET Core? – MindStick
Ask Question

How to configure Hangfire with SQL Server and dashboard authorization in ASP.NET Core?

Ravi Vishwakarma 319 17 Sep 2026

I am trying to integrate Hangfire into my ASP.NET Core Web API project for background processing. While basic setup works with memory storage, I need to configure it with SQL Server storage and restrict access to the dashboard.

Setting Up Hangfire Services

Here is my current setup in Program.cs:

// Add Hangfire services to DI container
builder.Services.AddHangfire(config => 
    config.UseSqlServerStorage(builder.Configuration.GetConnectionString("HangfireConnection")));

// Add the processing server
builder.Services.AddHangfireServer();

Restricting Dashboard Access

By default, the Hangfire dashboard is only accessible locally. How can I implement a custom IDashboardAuthorizationFilter to ensure only authorized admin users can view the dashboard in production?

  • What is the recommended approach to extract authenticated claims inside the authorization filter?
  • Are there performance implications when using SQL Server for high-frequency recurring jobs?
Hangfire
Ravi Vishwakarma
Ask by Ravi Vishwakarma
Updated 18 Oct 2026

1 Answers

Laura De Rosa
Laura De Rosa 18 Oct 2026
Report Abuse

Hangfire can store its jobs in SQL Server and run a dashboard inside an ASP.NET Core app. The dashboard is an administrative interface, so protect it with your app’s existing authentication rather than exposing it to every visitor.

Install the packages

Add Hangfire.AspNetCore and Hangfire.SqlServer to the project. Keep their versions aligned, and make sure the SQL Server connection string points to a database the application can access.

Register Hangfire and the SQL Server storage

In Program.cs, register Hangfire’s storage and server services. The server service is what processes queued jobs.

using Hangfire;
using Hangfire.Dashboard;

var builder = WebApplication.CreateBuilder(args);

var connectionString = builder.Configuration
    .GetConnectionString("Hangfire")
    ?? throw new InvalidOperationException("Missing Hangfire connection string.");

builder.Services.AddHangfire(configuration => configuration
    .UseSimpleAssemblyNameTypeSerializer()
    .UseRecommendedSerializerSettings()
    .UseSqlServerStorage(connectionString));

builder.Services.AddHangfireServer();

// Configure your app's authentication and authorization services here.
builder.Services.AddAuthentication(/* your scheme */);
builder.Services.AddAuthorization();

var app = builder.Build();

app.UseAuthentication();
app.UseAuthorization();

// Register the dashboard after authentication middleware.
app.UseHangfireDashboard("/hangfire", new DashboardOptions
{
    Authorization = new[] { new HangfireAdminFilter() }
});

app.Run();

public sealed class HangfireAdminFilter : IDashboardAuthorizationFilter
{
    public bool Authorize(DashboardContext context)
    {
        var user = context.GetHttpContext().User;

        // Require a signed-in user with the administrative role.
        return user.Identity?.IsAuthenticated == true
            && user.IsInRole("Admin");
    }
}

Replace the authentication placeholder with the scheme your app actually uses, such as ASP.NET Core Identity or cookie authentication. The role check also assumes authenticated users receive an Admin role claim. If your app uses a different authorization rule, adapt the filter to match it.

Put the connection string under the Hangfire name in configuration, and keep production credentials in a secret store or environment variables rather than committing them to source control. Hangfire can create or update its SQL Server schema when it connects, so the database account needs the required permissions.

With this setup, the dashboard is available at /hangfire and is restricted to authenticated administrators. Avoid an allow-all dashboard filter in production; the dashboard can expose job details and provide controls for managing background work.

advertising
Markdown for AI

A clean, structured version of this page for AI assistants and LLMs.

Open .md