-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
Not defined
Context:
It will be possible to disable multi tenancy in C8, to do so it was decided that each component has their own flag that determines whether multi tenancy is disabled or not. Optimize also needs such a config flag.
When multi tenancy is disabled, Optimize will still import tenantIds if present but does not need to fetch tenant authorizations or display tenant information in the UI.
AT:
- a config setting exists to enable/disable multi tenancy in Optimize:
CAMUNDA_OPTIMIZE_MULTITENANCY_ENABLED - the isMultiTenantEnvironment flag of the UI config is set in accordance with the multi_tenancy_enabled config setting
- this is added to the documentation ticket
Testing:
can be covered with the test cases in OPT-7124
This is the controller panel for Smart Panels app
[OPT-7268] Add config flag to disable multi tenancy C8
| Status | Original: Triage [ 10612 ] | New: Ready [ 10005 ] |
| Description |
Original:
*Context:*
It will be possible to disable multi tenancy in C8, to do so it was decided that each component has their own flag that determines whether multi tenancy is disabled or not. Optimize also needs such a config flag. When multi tenancy is disabled, Optimize will still import tenantIds if present but does not need to fetch tenant authorizations or display tenant information in the UI. *AT:* * a config setting exists to enable/disable multi tenancy in Optimize * this is added to the documentation ticket |
New:
*Context:*
It will be possible to disable multi tenancy in C8, to do so it was decided that each component has their own flag that determines whether multi tenancy is disabled or not. Optimize also needs such a config flag. When multi tenancy is disabled, Optimize will still import tenantIds if present but does not need to fetch tenant authorizations or display tenant information in the UI. *AT:* * a config setting exists to enable/disable multi tenancy in Optimize * the isMultiTenantEnvironment flag of the UI config is set in accordance with the multi_tenancy_enabled config setting * this is added to the documentation ticket |
| Status | Original: Ready [ 10005 ] | New: In Development [ 10312 ] |
| Status | Original: In Development [ 10312 ] | New: In Review [ 10212 ] |
| Assignee | Original: Helene Waechtler [ helene.waechtler ] | New: Giuliano Rodrigues Lima [ giuliano.rodrigues-lima ] |
| Assignee | Original: Giuliano Rodrigues Lima [ giuliano.rodrigues-lima ] | New: Helene Waechtler [ helene.waechtler ] |
| Description |
Original:
*Context:*
It will be possible to disable multi tenancy in C8, to do so it was decided that each component has their own flag that determines whether multi tenancy is disabled or not. Optimize also needs such a config flag. When multi tenancy is disabled, Optimize will still import tenantIds if present but does not need to fetch tenant authorizations or display tenant information in the UI. *AT:* * a config setting exists to enable/disable multi tenancy in Optimize * the isMultiTenantEnvironment flag of the UI config is set in accordance with the multi_tenancy_enabled config setting * this is added to the documentation ticket |
New:
*Context:*
It will be possible to disable multi tenancy in C8, to do so it was decided that each component has their own flag that determines whether multi tenancy is disabled or not. Optimize also needs such a config flag. When multi tenancy is disabled, Optimize will still import tenantIds if present but does not need to fetch tenant authorizations or display tenant information in the UI. *AT:* * a config setting exists to enable/disable multi tenancy in Optimize * the isMultiTenantEnvironment flag of the UI config is set in accordance with the multi_tenancy_enabled config setting * this is added to the documentation ticket Testing: can be covered with the test cases in |
| Assignee | Original: Helene Waechtler [ helene.waechtler ] | New: Cigdem Ilhan [ cigdem.ilhan ] |
| Status | Original: In Review [ 10212 ] | New: Ready for Testing [ 10008 ] |
| Description |
Original:
*Context:*
It will be possible to disable multi tenancy in C8, to do so it was decided that each component has their own flag that determines whether multi tenancy is disabled or not. Optimize also needs such a config flag. When multi tenancy is disabled, Optimize will still import tenantIds if present but does not need to fetch tenant authorizations or display tenant information in the UI. *AT:* * a config setting exists to enable/disable multi tenancy in Optimize * the isMultiTenantEnvironment flag of the UI config is set in accordance with the multi_tenancy_enabled config setting * this is added to the documentation ticket Testing: can be covered with the test cases in |
New:
*Context:*
It will be possible to disable multi tenancy in C8, to do so it was decided that each component has their own flag that determines whether multi tenancy is disabled or not. Optimize also needs such a config flag. When multi tenancy is disabled, Optimize will still import tenantIds if present but does not need to fetch tenant authorizations or display tenant information in the UI. *AT:* * a config setting exists to enable/disable multi tenancy in Optimize: CAMUNDA_OPTIMIZE_MULTITENANCY_ENABLED * the isMultiTenantEnvironment flag of the UI config is set in accordance with the multi_tenancy_enabled config setting * this is added to the documentation ticket Testing: can be covered with the test cases in |