Hangfire Background Job Manager
Hangfire is an advanced background job manager. You can integrate Hangfire with the ABP to use it instead of the default background job manager. In this way, you can use the same background job API for Hangfire and your code will be independent of Hangfire. If you like, you can directly use Hangfire's API, too.
See the background jobs document to learn how to use the background job system. This document only shows how to install and configure the Hangfire integration.
Installation
It is suggested to use the ABP CLI to install this package.
Using the ABP CLI
Open a command line window in the folder of the project (.csproj file) and type the following command:
If you haven't done it yet, you first need to install the ABP CLI. For other installation options, see the package description page.
Manual Installation
If you want to manually install;
Add the Volo.Abp.BackgroundJobs.HangFire NuGet package to your project:
Install-Package Volo.Abp.BackgroundJobs.HangFire
Add the
AbpBackgroundJobsHangfireModule
to the dependency list of your module:
Configuration
You can install any storage for Hangfire. The most common one is SQL Server (see the Hangfire.SqlServer NuGet package).
After you have installed these NuGet packages, you need to configure your project to use Hangfire.
1.First, we change the Module
class (example: <YourProjectName>HttpApiHostModule
) to add Hangfire configuration of the storage and connection string in the ConfigureServices
method:
You have to configure a storage for Hangfire.
- If you want to use hangfire's dashboard, you can add
UseAbpHangfireDashboard
call in theOnApplicationInitialization
method inModule
class:
Specifying Queue
You can use the QueueAttribute
to specify the queue:
Dashboard Authorization
Hangfire Dashboard provides information about your background jobs, including method names and serialized arguments as well as gives you an opportunity to manage them by performing different actions – retry, delete, trigger, etc. So it is important to restrict access to the Dashboard. To make it secure by default, only local requests are allowed, however you can change this by following the official documentation of Hangfire.
You can integrate the Hangfire dashboard to ABP authorization system using the AbpHangfireAuthorizationFilter
class. This class is defined in the Volo.Abp.Hangfire
package. The following example, checks if the current user is logged in to the application:
AbpHangfireAuthorizationFilter
is an implementation of an authorization filter.
AbpHangfireAuthorizationFilter
AbpHangfireAuthorizationFilter
class has the following fields:
enableTenant
(bool
, default:false
): Enables/disables accessing the Hangfire dashboard on tenant users.requiredPermissionName
(string
, default:null
): Hangfire dashboard is accessible only if the current user has the specified permission. In this case, if we specify a permission name, we don't need to setenableTenant
true
because the permission system already does it.
If you want to require an additional permission, you can pass it into the constructor as below:
Important: UseAbpHangfireDashboard
should be called after the authentication and authorization middlewares in your Startup
class (probably at the last line). Otherwise,
authorization will always fail!
Dashboard Authorization In API Projects
If you use the hangfire dashboard in an API project that uses non-cookie authentication (like JWT Bearers), The /hangfire
page can't authenticate the user.
In this case, you can add a cookies authorization scheme to authenticate the user. The best way to do this is to use the Cookie
and OpenIdConnect
authentication schemes. This requires creating a new OAuth2 client and adding the ClientId
, and ClientSecret
properties to the AuthServer
section in the appsettings.json
file.
The final code should look like below: