generate new app solution with abp studio Add a method to an appservice Execute method via swagger Receive antiforgery token error.
2024-11-22 11:36:09.728 -07:00 [WRN] The required antiforgery header value "RequestVerificationToken" is not present.
2024-11-22 11:36:09.729 -07:00 [INF] Authorization failed for the request at filter 'Volo.Abp.AspNetCore.Mvc.AntiForgery.AbpAutoValidateAntiforgeryTokenAuthorizationFilter'.
2024-11-22 11:36:09.730 -07:00 [INF] Executing StatusCodeResult, setting HTTP status code 400
Was this broken again with the move to 9?
similar to old post where this was already fixed in v4 https://abp.io/support/questions/554/REST-API-Antiforgery-Cookie-Error-After-POST-apiLogin---POST-apimyentity-Call-Sequence
We don't want a user to login, as our addon will run for many users and all of the communication that addon initiates with the abp backend, should be for the same tenant (but not specific to the user). Our addon will be used by many tenants in the same environment, the tenant's configuration details would be saved in the db the addon connects to (separate from abp) and retrieved on addon startup to make api calls to abp backend using the dynamic proxy application services. Could you help us with a poc for this?
hi
Both
Dynamic C# API Client ProxiesandStatic C# API Client Proxiescan be used.https://abp.io/support/questions/1727/How-to-build-winform-application-client-for-Dynamic-C-API-Client-Proxies
@mali, I think the question focuses most on the appropriate way to use the same and ensure the client is communicating with the correct tenant.
the service is one saas, and each customer will receive the client application, they will have to plug in some configuration values like the application id/ secret etc. And how to make sure their client only communicates with their tenant data?
as you can see our module solution comes from the previous abp design of modules where there were the **src **projects and the several **host **projects in the module solution. to completely develop and test the module we use the host solution as we would an "application" solution. therefore the module and host have the dependencies we plan to use once we integrate our module into any other app solution. for example this module can be integrated to 3 4 5 other app solutions (at least that was the idea with modules right?)
I see in the latest version of solutions generated now by abp studio (since we can no longer generate anything in suite), creation of module doesnt have any host project and its just library projects for app project, but that means usability amongst other app projects is out of the question?
Either way, if you're saying from now on our module projects cannot use already implemented modules from abp, then how do we code functionality in our modules that consumes that? for example the module provides all of the functionality related to docusign, like the app services that are exposed, events that are triggered and jobs that are handled, not the application project the application solution will bring in other modules that provide their respective functionality like this..
Could you provide a process or flow of how we should develop these modules to make sure they don't clash?
Also, could you provide a process flow for how you found the root problem in this ticket? It will help us with our troubleshooting before opening tickets in the future.
I added this and i can see entry in debug log during project startup regarding hangfire. two questions
Hangfire.SqlServer.SqlServerObjectsInstaller: Information: Hangfire SQL objects installed.
Hangfire.BackgroundJobServer: Information: Starting Hangfire Server using job storage: 'SQL Server: (LocalDb)\MSSQLLocalDB@Cloudapps'
Hangfire.BackgroundJobServer: Information: Using the following options for SQL Server job storage: Queue poll interval: 00:00:00.
Hangfire.BackgroundJobServer: Information: Using the following options for Hangfire Server:
Worker count: 20
Listening queues: 'docusignsignatures', 'default'
Shutdown timeout: 00:00:15
Schedule polling interval: 00:00:15
I reshared projects with you
Mailed you
Created app solution, and included an existing module (if I run the module directly in its own solution everything works well)
The module provides some functionality to receive api call and eventually queue up a job in the system which goes to hangfire (this works on module host)
When using this in app solution, the background job is executed ( i can see the api calls that this background job makes going out) but nothing ends up in hangfire, i believe it is executing in the built in default in mem implementation instead of hangfire.
My app module has the same version of hangfire and hangfire.sqlserver installed as module, which are in sync for abp 8.3.2 and is decorated with
typeof(AbpBackgroundJobsHangfireModule),
typeof(AbpBackgroundJobsModule)
in configureservices
context.Services.AddHangfire(config =>
{
config.UseSqlServerStorage(configuration.GetConnectionString("Default"));
});
Configure<AbpHangfireOptions>(options =>
{
options.ServerOptions = new BackgroundJobServerOptions { Queues = new[] { DocusignConstants.DocusignQueue, "default" } };
});
Configure<AbpBackgroundJobWorkerOptions>(options =>
{
options.DefaultTimeout = 864000; //10 days (as seconds)
});
in OnApplicationInitialization app.UseAbpHangfireDashboard("/hangfire", options => { options.AsyncAuthorization = new[] { new AbpHangfireAuthorizationFilter(enableTenant: true) }; });
While i can log in and see the dashboard, it never receives jobs.
So not supported in the page then?
Thanks for your response, is this something wrong on my side or in component?