Question regarding DomainTenantResolveContributor

• How does auth with external providers work when you use DomainTenantResolveContributor? do we have to register new clients with redirect URL for each tenant or is there a way to reuse the single client with all the tenant? right now external auth fails when you use DomainTenantResolveContributor because the redirect URI will be wrong.

• Does the Domain resolver work in localhost? if not how can I achieve it?

Here is what I have tried as of now.

            Configure<AbpTenantResolveOptions>(options =>
            {
                options.TenantResolvers.Insert(1, new DomainTenantResolveContributor("{0}.localhost:44311"));
            });

and this

options.AddDomainTenantResolver("{0}.localhost:44311");

Both options didn't work for me.

Start with DomainTenantResolveContributor, Configure, and AddDomainTenantResolver using the localhost examples in the issue. Trace how tenant resolution affects external-auth redirect URIs, then document the supported behavior for per-tenant clients, shared clients, and localhost; done means the issue's questions have a clear, reproducible answer.