Application multi-tenancy

[BrennanConroy]

Host multiple apps behind a single server.

• Host name routing?
• New UseStartup API?
• Auth will be fun!
• Different config/config sections

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[blowdart]

Host name routing?

Too simple. Some folks do it via a property in a cookie, some via parameters. Rather than just host header, have a tenant resolver function/delegate that people can implement how they like.

[blowdart]

Also, identity will need a lot of work (I had an email this morning, hi Carl!), if the expectation is to share one database per tenant.

[brockallen]

Isn't the real solution to make the DI system more flexible?

[AndrewTriesToCode]

I have a library that handles this pretty well if it offers any inspiration. It's currently being reviewed by the .NET Foundation.

It does:
Per-tenant authentication,
per-tenant options via DI (via a custom options factory)
shared EF Core database, separate db per tenant, or hybrid (and Identity support)
and a bunch of "strategies" like host/route/header resolution.

I don't do per-tenant configuration sections because I consider that to be more "app" than "tenant" related. The philosophy is geared more toward using per-tenant options for tenant specific behavior.

@brockallen as an aside I get asked all the time about plugging this into IdentityServer. I've had some limited success so far but have more things to figure out

https://github.com/Finbuckle/Finbuckle.MultiTenant