Are the designer/task webapps multi tenant enabled?

jckermagoret · January 16, 2019, 5:14pm

Hello,
I read in a few posts tenancy seems to be operational but it’s not clear at which level.

Is it possible to set tenant for users so they only see:

in the modeler webapp: processes related to their tenant
in the task webapp: tasks and processes related to their tenant

Is it available out of the box? Does it need to update the database? Add a column?

Thanks

JC

jckermagoret · January 21, 2019, 5:08pm

Any ideas about this question?

Thanks

Robinyo · January 23, 2019, 8:45pm

See:

ruzkant · January 28, 2019, 7:57am

Multi tenancy is mainly well supported on the engine and API level.

The modeler app however can be configured to support multi tenancy. Out of the box you have to configure a specific tenant_id for the modeler app, which means you need to deploy an instance per tenant in that scheme.

This was the pull request:

You set the flowable.common.app.tenant-id property in the application properties:

github.com

flowable/flowable-engine/blob/eeebfd23af3571741b60e3f663f17c0ecc50a812/modules/flowable-ui-modeler/flowable-ui-modeler-app/src/main/resources/flowable-default.properties

server.port=8888
server.servlet.context-path=/flowable-modeler
management.endpoints.jmx.unique-names=true
# This is needed to force use of JDK proxies instead of using CGLIB
spring.aop.proxy-target-class=false
spring.aop.auto=false
spring.application.name=flowable-ui-modeler
#
# SECURITY
#
spring.security.filter.dispatcher-types=REQUEST,FORWARD,ASYNC
spring.liquibase.enabled=false
spring.banner.location=classpath:/org/flowable/spring/boot/flowable-banner.txt
# The default domain for generating ObjectNames must be specified. Otherwise when multiple Spring Boot applications start in the same servlet container
# all would be created with the same name (com.zaxxer.hikari:name=dataSource,type=HikariDataSource) for example
spring.jmx.default-domain=${spring.application.name}

# Expose all actuator endpoints to the web
# They are exposed, but only authenticated users can see /info and /health abd users with access-admin can see the others
management.endpoints.web.exposure.include=*

This file has been truncated. show original

If you are willing to modify the modeler code you can create your own implementation of the org.flowable.app.tenant.TenantProvider interface to determine the tenant id. (For me I have my own distribution of the app that uses keycloak for user authentication and authorization and built my own tenant provider accordingly)

To the best of my knowledge the task app does not yet support multi tenancy out of the box. At some point I saw that tenant_id has been added as a column to the user table in the idm app, so I expect some contribution could be made there to pull that into the modeler and task apps, or maybe they have it in the pipeline…

Topic		Replies	Views
Flowable multi tenancy for all apps	3	816	April 18, 2023
Multi-tenancy support for Flowable Modeler app Flowable Application	3	1234	January 24, 2018
Multi Tenant Multi Schema with Shared Engine and supporting UIs Flowable Engine	2	651	October 7, 2020
Multitenancy Flowable engine in Spring Reactive app Flowable Engine	4	1116	August 3, 2021
Support for additional multi-tenancy models? Flowable Engine	2	2110	January 3, 2017

Are the designer/task webapps multi tenant enabled?

Related topics