Base solution for your next web application
Open Closed

ANZ for managing tenants with other applications #7258


User avatar
0
mac created

We're intending to use our first instance of ANZ to manage tenants and their applications that are separate from this instance. This means we want to be able to view tenants, manage their subscriptions, etc. But we don't want this instance to be multi-tenant.

From what I can tell, to do this, we'll need to enable the tenant management screens, but disable any form of actual multi-tenancy (such as separate databases, etc.)

What should we look at for that?

Thanks, //mac


1 Answer(s)
  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi @mac

    Unfortunately, there is no single setting which can achieve this easily.

    This means we want to be able to view tenants, manage their subscriptions, etc. But we don't want this instance to be multi-tenant.

    If you disalbe multi tenancy, it will cause some unexpected problems. The best option is to create a custom implementation of ITenantResolveContributor and return null in every case. Of course, your custom implementation must be used only for this instance.

    Another approach would be using tenancy name as subdomains, so each tenant can access to the app using {TENANCY_NAME}.mywebsite.com (instance #1) and host can access to the app using mywebsite.com (instance #2). If you do it like this, you don't have to write any additional code.