Activities of "alex.maiereanu@3sstudio.com"

Yeah, it's clear that we are going to see internal abp workers, but right now I think that Activate<HangfirePeriodicBackgroundWorkerAdapter<BackgroundJobWorker>>() is not doing anything, since we don't have internally any PeriodicBackgroundWorkers , we always use HangfirePeriodicBackgroundWorkerAdapter

Hi Frontis,

Thanks for doing the research. The repository seems out of date and I wouldn't base a solution on this.

Hi Maliming,

I don't want to set a new name, I want to get rid of HangfirePeriodicBackgroundWorkerAdapter from the hangfire dashboard because it's generating a flood of executed jobs, which eat up the ones that we care about.

Is it actually necessary to run HangfirePeriodicBackgroundWorkerAdapter if we use only HangfireBackgroundWorkerBase

Hi ABP team,

I have a question regarding HangfirePeriodicBackgroundWorkerAdapter. I understand this is a worker which is asking as a bridge. What I don't find so nice about this approach is that it's flooding the hangfire dashboard, and if somebody wants to check jobs of the application it's difficult to find them.

If someone would use directly HangfireBackgroundWorkerBase , would HangfirePeriodicBackgroundWorkerAdapter actually be necessary? And if no, can it be disabled?

Hi,

Thanks for the confirmation. Please refund the ticket :)

Hi,

I'm following up this ticket: https://abp.io/support/questions/8987/Upgrade-91---Issues-with-Google-External-login-Provider

Can you confirm that either 9.1.1 or 9.2 contains the bug fix for the above issues?

Thanks Alex

Hi, is this also fixing the issue that on migration to 9.1 the old values are not usable anymore? Or we need to reconfigure them?

I understand that this is a security measure but this should have been part of the migration guide so that we know what we are signing up to :D

Thanks

• Database System: EF Core / SQL Server , Running Angular UI

• Exception message and full stack trace: [10:02:58 INF] Error from RemoteAuthentication: OAuth token endpoint failure: invalid_client;Description=Unauthorized. [10:02:58 ERR] An unhandled exception has occurred while executing the request. Microsoft.AspNetCore.Authentication.AuthenticationFailureException: An error was encountered while handling the remote login. ---> Microsoft.AspNetCore.Authentication.AuthenticationFailureException: OAuth token endpoint failure: invalid_client;Description=Unauthorized --- End of inner exception stack trace --- at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler1.HandleRequestAsync() at Volo.Abp.Account.Public.Web.ExternalProviders.AbpAccountAuthenticationRequestHandler2.HandleRequestAsync() at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context) at Volo.Abp.AspNetCore.Security.AbpSecurityHeadersMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<<CreateMiddleware>b__0>d.MoveNext() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.RequestLocalization.AbpRequestLocalizationMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<<CreateMiddleware>b__0>d.MoveNext() --- End of stack trace from previous location ---

• Steps to reproduce the issue:

Hi, we upgraded an older project from 8.1 to 9.1, by doing step by step upgrades. After upgrading from 9.0.4 to 9.1, the google external login stopped working. Actually there are 2 issues:

• First of all, we had to delete the configurations in AbpSettings DB because the solution would not start, complaining that the settings are not in correct format
• After deleting the settings, and reconfigure the external google sign in, we get the above error

I tested this with a fresh 9.1 build, and the issue is also there. Basically configure google signin here:

And then try to login in with google.

Hi Berkan,

What do you mean that you agreed on the opinion? From what I see there was no followup on that task :))