Page History
The DCM Maintenance App supports multi-tenancy for communication with the Case Engine, it's data sources and asynchronous messaging.
Enabling multi-tenancy
To enable multi-tenancy, the following properties should be provided in the configuration:
Code Block | ||||
---|---|---|---|---|
| ||||
blueriq: multi-tenancy: enabled: true allowed-tenants: - A - B |
Authentication
To be able to use the DCM Maintenance App, the user should be authenticated. This is done through Keycloak as explained in Blueriq Gateway and OAuth2 configuration. 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 path
The tenant claim can be customized using a JsonPath expression in the same way the roles-path and username-path can be set.
Code Block | ||||
---|---|---|---|---|
| ||||
blueriq: jwt: tenant-path: $.custom_tenant_claim_path |
RabbitMQ and MongoDB configuration
For RabbitMQ and MongoDB the properties need to be set per tenant as well.
...