Working local version using the claims queue

Author: humzamanzoor

ClaimsSolution.API/ClaimsSolution.API.csproj

@@ -4,7 +4,6 @@
     <TargetFramework>net8.0</TargetFramework>
     <Nullable>enable</Nullable>
     <ImplicitUsings>enable</ImplicitUsings>
-    <UserSecretsId>34e1382a-3084-424c-bf06-478ca4c5f717</UserSecretsId>
   </PropertyGroup>
 
   <ItemGroup>

ClaimsSolution.ClaimsProcessor/Program.cs

@@ -3,16 +3,22 @@
 using Microsoft.Extensions.DependencyInjection;
 using Microsoft.Extensions.Hosting;
 using ClaimsSolution.Common.Extensions;
+using ClaimsSolution.ClaimsProcessor.Middlewares;
+using ClaimsSolution.ClaimsProcessor.Services;
 
 var builder = FunctionsApplication.CreateBuilder(args);
 
 builder.ConfigureFunctionsWebApplication();
 
+builder.UseMiddleware<ExceptionHandlingMiddleware>();
+
 // Also here, handle this via Options pattern
 var tableConnectionString = builder.Configuration["AzureWebJobsStorage"]!;
 
 builder.Services.AddTableStorageRepository(tableConnectionString);
 
+builder.Services.AddScoped<IClaimProcessingService, ClaimProcessingService>();
+
 builder.Services
     .AddApplicationInsightsTelemetryWorkerService()
     .ConfigureFunctionsApplicationInsights();