Скачать или смотреть Making Microsoft Graph API Calls with Hangfire in ASP.NET Core

Learn how to successfully integrate Microsoft Graph API calls with `Hangfire` in your ASP.NET Core application, bypassing common issues such as null `HttpContext`.
---
This video is based on the question https://stackoverflow.com/q/66281237/ asked by the user 'Umar Yaqub' ( https://stackoverflow.com/u/7767426/ ) and on the answer https://stackoverflow.com/a/66561524/ provided by the user 'MickC' ( https://stackoverflow.com/u/9462739/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Making Microsoft Graph API call with Hangfire

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Making Microsoft Graph API Calls with Hangfire in ASP.NET Core

Integrating background job processing in your ASP.NET applications can be tricky, especially when it involves making API calls like those from Microsoft Graph. One common challenge developers face is executing these calls within a Hangfire background job, particularly due to issues related to HttpContext being null. In this post, we will explore how to work around these challenges and successfully schedule Microsoft Graph API calls with Hangfire.

Understanding the Problem

When you attempt to make a Microsoft Graph API call within a Hangfire background job, you may find that the usual access tokens are not available, and you get a response indicating that the context is not properly set.

A Common Scenario

[[See Video to Reveal this Text or Code Snippet]]

In this scenario, if you attempt to fetch user information from the Graph API, you may get a result indicating that the call is "Not yet computed." This typically occurs due to the loss of context and authorization token when executing in the background.

The Solution: Access Tokens and Background Jobs

To solve this issue, the approach involves acquiring an access token for Microsoft Graph and using it to create a new instance of the Graph client within your background job.

Step 1: Configure Token Acquisition in Startup.cs

The first step is to allow your application to retrieve access tokens. You can do this by configuring the authentication middleware in your Startup.cs file:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Controller Initialization

Ensure that your controller is set up to handle token acquisition. Here’s a sample controller setup:

[[See Video to Reveal this Text or Code Snippet]]

Step 3: Schedule a Background Job

In your controller action, you can schedule a background job while handling the acquisition of the access token:

[[See Video to Reveal this Text or Code Snippet]]

Step 4: Implement the Background Job Class

You will need to create a class for your background job that consumes the Graph API:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

By leveraging token acquisition and creating an independent instance of the Graph client, you circumvent the issues associated with HttpContext in Hangfire background jobs. This approach ensures that your Microsoft Graph API calls are executed seamlessly without losing the necessary context for authentication.

Now you can confidently implement background jobs within your ASP.NET Core application while effectively integrating with Microsoft Graph API. Happy coding!