Activities of "JanneHarju"

• ABP Framework version: v8.0.5
• UI Type: Angular
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): Separated
• Exception message and full stack trace:

DependencyResolutionException: None of the constructors found on type 'Volo.Abp.Account.Public.Web.ExternalProviders.AccountExternalProviderOptionsManager`1[Microsoft.AspNetCore.Authentication.Google.GoogleOptions]' can be invoked with the available services and parameters:
Cannot resolve parameter 'Volo.Abp.Account.ExternalProviders.IAccountExternalProviderAppService accountExternalProviderAppService' of constructor 'Void .ctor(Microsoft.Extensions.Options.IOptionsFactory`1[Microsoft.AspNetCore.Authentication.Google.GoogleOptions], Volo.Abp.Account.ExternalProviders.IAccountExternalProviderAppService, Volo.Abp.Security.Encryption.IStringEncryptionService, Volo.Abp.MultiTenancy.ITenantConfigurationProvider, System.Collections.Generic.IEnumerable`1[Volo.Abp.Account.Public.Web.ExternalProviders.IPostConfigureAccountExternalProviderOptions`1[Microsoft.AspNetCore.Authentication.Google.GoogleOptions]])'.

Stack trace:

See https://autofac.rtfd.io/help/no-constructors-bindable for more info.
   at Autofac.Core.Activators.Reflection.ReflectionActivator.<>c__DisplayClass14_0.<UseSingleConstructorActivation>b__0(ResolveRequestContext context, Action`1 next)
   at Autofac.Core.Resolving.Middleware.DelegateMiddleware.Execute(ResolveRequestContext context, Action`1 next)
   at Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.<>c__DisplayClass14_0.<BuildPipeline>b__1(ResolveRequestContext context)
   at Autofac.Core.Resolving.Middleware.DisposalTrackingMiddleware.Execute(ResolveRequestContext context, Action`1 next)
   at Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.&lt;&gt;c__DisplayClass14_0.&lt;BuildPipeline&gt;b__1(ResolveRequestContext context)
   at Autofac.Builder.RegistrationBuilder`3.<>c__DisplayClass41_0.<PropertiesAutowired>b__0(ResolveRequestContext context, Action`1 next)
   at Autofac.Core.Resolving.Middleware.DelegateMiddleware.Execute(ResolveRequestContext context, Action`1 next)
   at Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.<>c__DisplayClass14_0.<BuildPipeline>b__1(ResolveRequestContext context)
   at Autofac.Builder.RegistrationBuilder`3.&lt;&gt;c__DisplayClass39_0.&lt;OnActivated&gt;b__0(ResolveRequestContext context, Action`1 next)
   at Autofac.Core.Resolving.Middleware.CoreEventMiddleware.Execute(ResolveRequestContext context, Action`1 next)
   at Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.&lt;&gt;c__DisplayClass14_0.&lt;BuildPipeline&gt;b__1(ResolveRequestContext context)
   at Autofac.Core.Resolving.Middleware.ActivatorErrorHandlingMiddleware.Execute(ResolveRequestContext context, Action`1 next)

• Steps to reproduce the issue: Update project to 8.1.1 and then downgrade to 8.0.5. After that start project and navigate to AuthServer login page. You get given error message.

I was upgrading our project from 7.4 to 8.1.0 but after we notice that there were severe EF performance problem I tried to update to 8.1.1 but still performance problem. After that I tried to downgrade to 8.0.5 but then I got this error message. 8.0.5 downgrade fixed our performance problem but login page is not working. If you don't have any problem with 8.0.5 then is there any other options than to start update process all over again from 7.4 to 8.0 or wait until 8.1.2 is published and hopefully performance problem is gone. I was thinking is there some changes in 8.1 AuthServer version which might not work with 8.0 version. I think abp update command change AuthServer code when I updated to 8.1 version.

Ok. Thanks anyway.

Is it OK to clean it away in our own code? https://scm-test.lw.app/? code=0m3Bw75YTPhX5MPp2lmcGhiU4igYl1YMRWDbD0QIEMA& state=dmxqdENEanJ1ZWFseU5sTGZjRXZpZklDYnQ5Ni5Cemg3dFBWcC1vN3Bja2V5& iss=https%3A%2F%2Fauth.scm-test.lw.app%2F

These are what AuthServer returns in callback call. Code and state are removed from url by your code or open iddicts but iss stays.

Is it normal/correct that after login there is iss url parameter like this: https://scm-test.lw.app/app/?iss=https:%2F%2Fauth.scm-test.lw.app%2F ?

Actually I forget that there was override for AuthServer:Authority parameter at Host App Service Configuration and it was https://app-scm-auth-test-qa-001.ase-sharedeawgeacbyumuk-qa-001.appserviceenvironment.net/ because that way communication goes directly to auth server inside Azure that why we cannot use public address(https://auth.scm-test.lw.app) because it is IP restricted. After I added that setIssuer to AuthServer code it started to work. At AuthServer AuthServer:Authority parameter value is https://auth.scm-test.lw.app/. So now it started to work. So there was no need for that Configure part. SetIssuer was all I needed.

builder.Configure(c =>
    {
        c.TokenValidationParameters.ValidIssuers = new List<string>()
        {
            configuration["AuthServer:Authority"]!,
            "https://app-scm-auth-test-qa-001.ase-sharedeawgeacbyumuk-qa-001.appserviceenvironment.net/"
        };
    });

Thanks.

Thank you for the tip. Actually in my stash I did have that setIssuer because there was that line in example project what I created with abp suite, but I wasn't sure was that needed because there wasn't anything in migration guide and there was not need for it with IdentityServer. I will first only add it and if it doesn't work then I will add that configure part.

here is example token payload. If it tells you enything.

{
  "sub": "f6277149-bcd8-7587-5001-3a096665a3a1",
  "preferred_username": "admin",
  "email": "SCMadmin@leanware.fi",
  "role": "admin",
  "given_name": "admin",
  "phone_number_verified": "False",
  "email_verified": "False",
  "unique_name": "admin",
  "oi_prst": "SCM_App",
  "iss": "https://auth.scm-test.lw.app/",
  "oi_au_id": "0a696354-cb8f-b108-c129-3a666cdeae51",
  "client_id": "SCM_App",
  "oi_tkn_id": "5ba7a0c9-4577-a3ea-a15a-3a666ab74e8c",
  "aud": "SCM",
  "scope": "offline_access openid profile roles email phone SCM",
  "jti": "fe00a5cf-c813-4713-9219-85e04666cc29",
  "exp": 1702564553,
  "iat": 1702560953
}

We have Application Gateway which direct calls to App service. That appserviceenvironment.net is app service address. And lw.app is Application gateway address. Can you tell me is that Issuer: 'https://auth.scm-test.lw.app/' value from fronend Authority parameter? And can you tell me where this value is coming from validationParameters.ValidIssuers: 'https://app-scm-auth-test-qa-001.ase-sharedeawgeacbyumuk-qa-001.appserviceenvironment.net/'? I mean from what configuration. Appsettings.json?, database? Because I'm sure that there is no where that exact value. But in earlier project when some url changed from lw.app to appserviceenvironment.net there was missing trailing / . And adding / fixed. So now I'm wondering is it same problem and if it is where I'm missing that / . Because I think I have added it to all places.

Here are logs when I did one login. There was on ly csv export possibility in our logging tool, but I copied data from there to txt format if you prefer it. https://drive.google.com/drive/folders/1yTPoOMqUpcpTjlXgdEKsSJahgIRTd65A?usp=drive_link

Those logs what I give has all related logs what happened when I start to login give correct account informations and return back to application. Because there was so much logs I filtered these kind of lines away because I assume they are not related to this issue: customDimensions.SourceContext !contains "HealthChecks" and message != "Added 0 entity changes to the current audit log" and message !contains "Added bundle 'Lepton.Global'"