Hi Ricardo,
This is the kind of topic I like, because a simple question can lead to a nice discussion. :)
Yes, here we also use Single Tenant modules in Multi-Tenant applications. The documentations is misleading there.
And yes, here we also use Single Tenant User Provider modules to isolate applications. But in our case, those applications are not Multi-Tenant.
In your scenario, Norris_UserProvider being Single Tenant seems to not have any impact, as all the Applications the customer uses are also Single Tenant (missing the Tenant tab will not have impact).
But in the case of the Chuck customer, as he is using a Multi-Tenant application (App1), using a Multi-Tenant User Provider is the way to go (in my opinion). And there is no reason to be different, as the isolation and single sign-on will still be there, because you are using different User Providers.
What I didn't understand of the scenario is why App1 is multi-tenant. You want to use this app with other future customers?
And why the App2 is Single Tenant. Is it a back office for the customer or for the company? In any case, and here I'm speculating because I never used a single tenant module in a multi-tenant application (and didn't tested it), I think it wont matter, as the tenant is bound to the user, not the app/module, and when the user creates data in local entities, the visibility will depend on the entity tenant status (is it single tenant as in the module it is or it is marked as multi-tenant?).
Well, thanks for the discussion. :)
Multi-Tenancy is not wide spread used and I think the reason is exactly because it is not easy to fully grasp its concept.
Cheers,
Eduardo Jauch