Multitenancy support

[petermasking]

URL based. Styling and data.

(needs refinement)

[basmasking]

I've done some refinement on the datamodel and how we can incorporate the tenant id into our application.

For the multi-tenancy support we can make the decision to really have a separate account for each tenant. The email address of the user, together with the tenant id would specify the uniqueness of the account. This setup would be easy, as it doesn’t require any of the tenant ids to bleed through in the data. The downside of this approach is that the user might perceive a sub domain as part of the comify application, but in fact has multiple accounts and needs to update all of them separately.

The other option we can choose from, is the idea that the user will only have a single account and is linked to other tenants based on a list of tenant ids the user belongs to. In this case the user really has a single account, and only a single account needs to be maintained. The downside of this is that the tenant id needs to be stored for some, or all, or our data model definitions.

In case we take the linked list approach, we need to add a new data object to our domain model, which is the tenant. The sub domain / url of the instance will be stored here, together with a unique id that will be used as a reference. We might need to have an option to add more details about each tenant in the future, adding new functionality in the webui.

The following objects are a minimum where we need to add the tenant id to, because these are queried directly from the front end.

• creator
• creator.metrics
• notification
• post
• post.metrics
• relation

For the authentication it means that the tenant id is used for redirecting urls and the middleware has to solve it.

The creator will get a list of tenant ids the user belongs to. The other objects mentioned will only get a single tenant id for the tenant the object has been made for.

[basmasking]

I've started implementing this issue, and there is one thing I have to do for all functions that are exposed on the bff.

During login, the tenant id will be populated and added to the requester object on the gateway. This object is automatically inserted in locations where it's needed. So, to get the requester in the function, it needs to be defined on every function.