multi-tenant

I have an Asp.net application 3.5. I want to be able to allow multiple/ different clients to access the same application but using different URL's. I have already managed to configure the database to allow this. So here's the main part. I want to host my application in a domain say... wwww.myapplication.com then allow different client to access the same application using 1) www.clientOne.myapplication.com 2) www.clientTwo.myapplication.com Also the client subdomains i.e(clientone.myapplication.com and clienttwo.myapplication.com) should be autocreated by the client upon registration. How can I

I am attempting to build a multi-tenant application for Office 365 which focuses on SharePoint Online and authenticates through Azure using OAuth2. The problem is specific to SharePoint access via the Azure login, but is only found when using this API to authenticate using OAuth2. Many of the mechanics of registering the application properly and setting up users in Azure and Office, while somewhat complex, are conquerable with the right about of time investment. Even the basic OAuth2 protocol usage with Azure works relatively smoothly. However, I'm thwarted in making my application truly multi

Autofac 3.0 will have a MultitenantIntegration support and its preview release is out now. To try it out, I created an ASP.NET Web API application with the following configuration: public class Global : System.Web.HttpApplication { protected void Application_Start(object sender, EventArgs e) { var config = GlobalConfiguration.Configuration; config.Routes.MapHttpRoute("Default", "api/{controller}"); RegisterDependencies(config); } public void RegisterDependencies(HttpConfiguration config) { var builder = new ContainerBuilder(); builder.RegisterApiControllers(Assembly.GetExecutingAssembly()); //

I am trying to build and application using Laravel 5. It is supposed to be a multi tenant database architecture using multiple databases. My employer requires this for security purposes. I have tried manually managing the main DB migrations and the Tenant migrations but failed. So I decided to take the help of a Laravel specific package which is supposedly what I require. Tenanti provides a way to have my purpose solved but the problem is that me being a novice developer, am not able to fully understand how to use it in my application. I have installed it correctly I believe doing: composer

My organization needs to have a shared database, shared schema multitenant database. We will be querying based on TenantId. We will have very few tenants (less than 10) and all will share the same database schema with no support for tenant-specific changes or functionality. Tenant metadata will be stored in memory, not in the DB (static members). This means all entities will now need a TenantId, and DbContext needs to know to filter on this by default. The TenantId will likely be identified by a header value or the originating domain, unless there's a more advisable approach. I've seen various

I'm creating a multi tenant application like shopify and wanna know how can I create custom domain on server that points to the same application instance? For example: app1.mysystem.com == www.mystore.com app2.mystem.com == www.killerstore.com I need to do that config on CNAME like Google Apps? If so, how can I do that? Is there some good paper showing how this works ? PS: app1 AND app2 points to the same application! Thanks I have a similar setup and am using nginX. What I did for ease of maintenance was accepted all the connections from nginx and did the filtering in my app. # application

Over the past couple of years I have developed a very customised PHP/MySQL application that is used for a number of clients. I have been creating a new database and new installation for each client up to this point. The first obvious problem here is keeping multiple installations up to date with any code changes; a second problem is that each installation has a large amount of users; and for most clients; some of these users are the same - and they have to have a number of seperate user accounts and urls to remember. I am moving the application over to Laravel 5 at the moment and looking into

My goal is to have separate user accounts for each subdomain. Under no circumstance do I want cross-pollination between subdomains. I've looked over Robby Russle , and DHH's thoughts (both are pre-Rails3 though). The controller handling is pretty straight forward, my questions is about keeping the model's data separated. What's the best way to keep user1 from seeing user2's data? Some idea's might include: Add a subdomain_id foreign key to every model - Advantage , simple one-to-many relationship can be used to scope each model to a subdomain. - Disadvantage , this is pretty tight coupling

I'm writing a web app that supports multiple users. Each user has their own database - using H2. all database schemas are the same. I wish to use Spring + Hibernate for this application. So I'm stuck at how to associate a user's database with that user - maybe associated it in the HTTPSession, and extend spring's AbstractRoutingDataSource? but wouldn't this effect Hibernate's cache? Another way is to have a SessionFactory with each datasource, even though every datasource's schema is the same... so I see that as a waste. Anyways selecting the datasource needs to be dynamic - they can't be pre