Hangfire.Dashboard.Authorization 3.1.0

Prefix Reserved
dotnet add package Hangfire.Dashboard.Authorization --version 3.1.0                
NuGet\Install-Package Hangfire.Dashboard.Authorization -Version 3.1.0                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Hangfire.Dashboard.Authorization" Version="3.1.0" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Hangfire.Dashboard.Authorization --version 3.1.0                
#r "nuget: Hangfire.Dashboard.Authorization, 3.1.0"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Hangfire.Dashboard.Authorization as a Cake Addin
#addin nuget:?package=Hangfire.Dashboard.Authorization&version=3.1.0

// Install Hangfire.Dashboard.Authorization as a Cake Tool
#tool nuget:?package=Hangfire.Dashboard.Authorization&version=3.1.0                


Some authorization filters for Hangfire's Dashboard for .NET Framework-based ASP.NET Applications.


This library is available as a NuGet Package:

Install-Package Hangfire.Dashboard.Authorization


All the available classes implement both IAuthorizationFilter and IDashboardAuthorizationFilter interfaces, and compatible with Hangfire.Core 1.6 and later.

OWIN-based authentication

using Hangfire.Dashboard;

public void Configure(IAppBuilder app)
    var options = new DashboardOptions
        Authorization = new [] 
            new AuthorizationFilter { Users = "admin, superuser", Roles = "advanced" },
            new ClaimsBasedAuthorizationFilter("name", "value")
    app.UseHangfireDashboard("/hangfire", options);

Basic authentication

Note: If you are using basic authentication together with OWIN security, configure Hangfire BEFORE OWIN security configuration.

Please, keep in mind, if you have no SSL-based instance for your web application you have to disable SslRedirect and RequireSsl options (it's enabled by default for security reasons). Otherwise you will have dead redirect.

var filter = new BasicAuthAuthorizationFilter(
    new BasicAuthAuthorizationFilterOptions
        // Require secure connection for dashboard
        RequireSsl = true,
        // Case sensitive login checking
        LoginCaseSensitive = true,
        // Users
        Users = new[]
            new BasicAuthAuthorizationUser
                Login = "Administrator-1",
                // Password as plain text, SHA1 will be used
                PasswordClear = "test"
            new BasicAuthAuthorizationUser
                Login = "Administrator-2",
                // Password as SHA1 hash
                Password = new byte[]{0xa9,
                    0x4a, 0x8f, 0xe5, 0xcc, 0xb1, 0x9b,
                    0xa6, 0x1c, 0x4c, 0x08, 0x73, 0xd3,
                    0x91, 0xe9, 0x87, 0x98, 0x2f, 0xbb,

It is also possible to use other than SHA1 crypto provider by specifying it when creating a user:

var user = new BasicAuthAuthorizationUser(HMAC.Create)
    Login = "Admin",
    PasswordClear = "Password" // HMAC will be used instead

How to generate password hash

Just run this code:

string password = "<your password here>";
using (var cryptoProvider = System.Security.Cryptography.SHA1.Create())
    byte[] passwordHash = cryptoProvider.ComputeHash(Encoding.UTF8.GetBytes(password));
    string result = "new byte[] { " + 
        String.Join(",", passwordHash.Select(x => "0x" + x.ToString("x2")).ToArray())
         + " } ";

The result variable will contain byte array definition with your password.

Product Compatible and additional computed target framework versions.
.NET Framework net45 is compatible.  net451 was computed.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on Hangfire.Dashboard.Authorization:

Package Downloads

Package Description

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
3.1.0 30,763 3/22/2024
3.0.1 439,440 8/29/2022
3.0.0 1,074,836 1/23/2020
2.1.0 2,835,388 12/8/2014
2.0.0 27,706 9/5/2014
1.0.1 2,357 9/5/2014
1.0.0 3,902 6/30/2014
1.0.0-alpha1 1,511 6/30/2014


• Project – Full source link support with embedded symbols and repository-based sources.
• Project – Enable static analysis via the Microsoft.CodeAnalysis.NetAnalyzers package.
• Project – Sign NuGet package and .NET assemblies with a code signing certificate.
• Project – Require signature validation when restoring NuGet packages.
• Project – Use deterministic and locked package restore for projects.
• Project – Add more metadata for assemblies and NuGet package.

• Changed – Upgrade internal version of `Microsoft.Owin` package to 4.2.2.
• Security – Avoid CVE-2020-1045 vulnerability by upgrading `Microsoft.Owin` package.

• Added – All classes now implement `IDashboardAuthorizationFilter` interface appeared in Hangfire 1.6.0 (by @antonioseric, @spoofi).
• Added – It's possible to use custom crypto provider such as `HMAC` when creating a BasicAuth user (by @faizulhaque).
• Changed – Minimal `Hangfire.Core` package version is bumped to 1.6.0.
• Changed – Internalized `Microsoft.Owin` package version is now 3.1.0.
• Fixed – Remove `AssemblyFileVersion` attribute to avoid problems with installers and GAC (by @fire-eagle).
• Fixed – Different `README.md` updates and fixes (by @spoofi).
• Added – Basic authentication filter (by @sergun).
• Added – Check `Authentication.User` is not null in claims authorization filter (by @pjcunningham).