multi-tenant

I've been implementing DocumentDB during preview into a multi-tenent system. My plan has been to generate a new database under the DocumentDB account for each tenant that signs up. Most of this code is already in place and the testing is going extremely well. Since DocumentDB has been officially released and the documentation is finalized I read about the 100 database limit per DocumentDB account and it made me stop to rethink my architecture. I wanted to keep my tenants isolated so that deleting accounts would be easy, and the organization of it would be very clean. Data between tenants do

I have been following Ryan Boland's excellent Rails multitenancy tutorial , but have run into a snag with devise_invitable. I am using... Rails 4.1.5 devise 3.3.0 devise_invitable 1.3.6 Postgresql I create a new account and user/account owner on a chosen subdomain (mysubdomain.lvh.me:3000), from which I can send a user invitation just fine. I open the invitation link in an incognito Chrome session to ensure I am not logged in or have any current session. Upon clicking on the invitation link, I am redirected to the sign in page (mysubdomain.lvh.me:3000/users/sign_in) and see a flash notice:

I have developed a small webapp using and SpringMVC(3.1.3.RELEASE) and Hibernate 4.2.0.Final. I'm trying to convert it to be a multi-tenant application. Similar topics have been covered in other threads, but I couldn't find a definitive solution to my problem. What I am trying to achieve is to design a web app which is able to: Read a datasource configuration at startup (an XML file containing multiple datasource definitions, which is placed outside the WAR file and it's not the application-context or hibernate configuration file) Create a session factory for each one of them (considering that

I'm trying to implement an IdentityServer that handles an SSO for a multitenant application. Our system will have only one IdentityServer4 instance to handle the authentication of a multitentant client. On the client side, I'm using the acr_value to pass the tenant Id. A piece of code from the Startup.cs file is as follows: public void ConfigureServices(IServiceCollection services) { services.AddMvc(); services.AddAuthorization(); services.AddAuthentication(options => { options.DefaultScheme = "Cookies"; options.DefaultChallengeScheme = "oidc"; }) .AddCookie("Cookies") .AddOpenIdConnect("oidc"

I am migrating my multitenant application from Webapi to aspnet core. In webapi version I was using TenantIdentificationStrategy that identified tenants based on request path on HttpContext . Moving to aspnet core, I am able to wire-up autofac successfully. I am not able to figure out how to wireup the tenant strategy. I tried injecting IHttpContextAccessor in ConfigureServices as services.AddSingleton<IHttpContextAccessor, HttpContextAccessor>(); and my strategy looks like this public class AssetClassIdentificationStrategy: ITenantIdentificationStrategy { private readonly IHttpContextAccessor

First, let me start that I have looked so many sites about the "correct" way to configure multiple datasource on Grails, every one of them (with Grails 2.0 and later) pointing to the docs , however after doing what the docs says I get this error: Error 2014-03-29 15:48:29,219 [localhost-startStop-1] ERROR context.GrailsContextLoader - Error initializing the application: Error creating bean with name 'transactionManager_lookup': Cannot resolve reference to bean 'sessionFactory_lookup' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory

I would appreciate some pointers regarding data access/control in a MVC based multi tenant site: Is there a better/more secure/elegant way to make sure that in a multi tenant site the user can handle only its own data. There are number of tenants using same app: firstTenant.myapp.com, secondTenant.myapp.com... // // GET: /Customer/ // show this tenant's customer info only public ViewResult Index() { //get TenantID from on server cache int TenantID = Convert.ToInt16( new AppSettings()["TenantID"]); return View(context.Customers.ToList().Where(c => c.TenantID == TenantID)); } If a user logs in

I'm weighing up having separate DBs (one per company) vs one multi-tenanted DB (with all companies). Criteria: A user can belong to one company only and can't access documents of other companies. An administrator of the system needs to maintain DBs for all firms. Number of companies/tenants - from hundreds to tens of thousands There is one entry point with authentication, for all companies/tenants (it'll resolve the tenant and address it to the right DB). Question #1 . Are there any "good practices" for designing a multi-tenanted database in RavenDB? There is a similar post for MongoDB . Would