Aktivity „andmattia“

Ok

I try to check if this pattern can be use in our scenario

We found another issue.

If we try to execute the audit log from second app we see the host log. We check on DB and tenant filter not flow but if we do the same operation (same tenant) on first app we see only log for our tenant

No I've only one handler but it's in a module that I use twice.

Module product with handler ChangeProductHandler. I use this module on ERP and E-Commerce

I've 1 database anche 2 separate API/UI

Hi I know but I don't found any other solution

Hi

I found this possibile solution

.ConfigureWebHostDefaults(builder =>
            {
                builder.Configure(app =>
                {
                    app.UseRouting();

                    app.UseHangfireDashboard();
                    app.UseEndpoints(endpoints =>
                    {
                        endpoints.MapHangfireDashboard();
                    });
                });
            })

How can I inject Iconfiguration?

 public override async Task OnApplicationInitializationAsync(
        ApplicationInitializationContext context)
    {
        await context.AddBackgroundWorkerAsync<PollingWorker>();
    }

If I add an IServiceProvider I get this error

annot resolve parameter 'Microsoft.Extensions.DependencyInjection.IServiceCollection service' of constructor 'Void .ctor(Microsoft.Extensions.DependencyInjection.IServiceCollection)'.
   at Autofac.Core.Activators.Reflection.ReflectionActivator.GetAllBindings(ConstructorBinder[] availableConstructors, IComponentContext context, IEnumerable`1 parameters)
   at Autofac.Core.Activators.Reflection.ReflectionActivator.ActivateInstance(IComponentContext context, IEnumerable`1 parameters)
   at Autofac.Core.Activators.Reflection.ReflectionActivator.<ConfigurePipeline>b__11_0(ResolveRequestContext ctxt, Action`1 next)
   at Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.&lt;&gt;c__DisplayClass14_0.&lt;BuildPipeline&gt;b__1(ResolveRequestContext ctxt)

Hangfire

Hi

from my side it not works but I found this post and I remove

 responseType: 'code',

After that my login on angular side work I dont redirect me to IDS login page.

The issue still exists on API if I try to login from swagger the app redirect me to base auth and not to tenant auth

Hi

I see the same and it works but redirect me to IDS page e not to my local login in angular why?

I re check all configuration on my module and work (partially on Angular).

I need to add to environment.ts

skipIssuerCheck: true

After Add this my app will be redirect to correct Auth Server (es Tenant 1 (t1) -> https://t1.auth.mydomain.com) but I use the custom login into angular with customize Login/register page

export class AppComponent {
  constructor(private replaceableComponentsService: ReplaceableComponentsService) {}

  ngOnInit() {
    this.replaceableComponentsService.add({
      key: eAccountComponents.Login,
      component: LoginComponent,
    });
    this.replaceableComponentsService.add({
      key: eAccountComponents.Register,
      component: RegisterComponent,
    });
    this.replaceableComponentsService.add({
      key: eThemeLeptonComponents.AccountLayout,
      component: AccountLayoutComponent,
    });
  }
}

This work fine if I don't use a normal tenant selector but in tenant rosolve by name when I click login I'll be redirect to Auth (Mvc page and not to angular route). I doesn't work on tenant/host side

I look into the call /.well-known/openid-configuration and I see that and i console I read an error that

main.fbfd4e772f61baa1.js:1 invalid issuer in discovery document expected: https://t1.mydomain.com current: https://auth.mydomain.com

"issuer": "https://auth.mydomain.com",
"jwks_uri": "https://t1.auth.mydomain.com/.well-known/openid-configuration/jwks",
"authorization_endpoint": "https://t1.auth.mydomain.com/connect/authorize",
"token_endpoint": "https://t1.auth.mydomain.com/connect/token",
"userinfo_endpoint": "https://t1.auth.mydomain.com/connect/userinfo",
"end_session_endpoint": "https://t1.auth.mydomain.com/connect/endsession",
"check_session_iframe": "https://t1.auth.mydomain.com/connect/checksession",
"revocation_endpoint": "https://t1.auth.mydomain.com/connect/revocation",
"introspection_endpoint": "https://t1.auth.mydomain.com/connect/introspect",
"device_authorization_endpoint": "https://t1.auth.mydomain.com/connect/deviceauthorization",
"frontchannel_logout_supported": true,
"frontchannel_logout_session_supported": true,
"backchannel_logout_supported": true,
"backchannel_logout_session_supported": true,