Page History
Include Page | ||||
---|---|---|---|---|
|
To prepare your setup for multi tenancy you will need to execute some steps per component.
Most components in a setup make use of one or more Databases (SQL and/or NoSQL). Furthermore, AMQP can be used to communicate between the components.
In order to make sure that no tenant can access data of another tenant, each tenant will need their own databases. Thus, you will need to create them for each tenant. simply use the delivered create scripts to create the dedicated databases for each tenant.
For AMQP, you should also create the neccessary queues and exchanges per tenant for each component and configure the vHost to make sure that the correct messages are being sent to the correct tenant.
Enabling Multi tenancy
Include Page | ||||
---|---|---|---|---|
|
These properties are used in each component that is mentiond on this page.
X-Tenant-ID
Include Page | ||||
---|---|---|---|---|
|
This property can be used in each component that is mentiond on this page.
We advise to set up an HTTP server (for example NGINX or Apache HTTPD) which can be configured to add this HTTP header depending on, for instance, the url from which the Runtime is called.
Info |
---|
We only support multi-tenancy where each tenant uses the same database vendor. You are not able to mix, for example, an Oracle tenant with an Microsoft SQL Server tenant. |
Default configuration
Include Page | ||||
---|---|---|---|---|
|
UI Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
Authentication - OAuth2 and KeycloakIn single-tenant mode as well as in multi-tenancy mode, OAuth2 and Keycloak can be used for the authentication mechanism. The difference with multi-tenancy is that the application now expects a claim to be present in the JWT token with the claim path name "tenant" and with the tenant name as value. This claim name is customizable if the tenant is present in the JWT token with a different claim name. Customizing the tenant pathThe tenant claim can be customized using a JsonPath expression in the same way the roles-path and username-path can be set.
|
UI Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
UI Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
UI Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
UI Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
UI Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|