I am looking into the multi-tenancy feature and would like to ask a few questions.
1. Handling user tasks with multi-tenancy
Background info:
It is possible to query for user tasks via the Tasklist API (Search tasks | Camunda 8 Docs). Here a request parameter “tenantIds” exists. However, the endpoints in the Tasklist API as well as the endpoints of the Zeebe REST API for managing user tasks, only take a “taskId” as a parameter - there is no way to provide a tenant ID.
Question:
Does this mean that task IDs are unique across tenants? So it is not possible that two tenants each have a user task with the same ID?
2. Support for multi-tenancy
From my research on the topic of multi-tenancy I understand that multi-tenancy is currently only supported for Self-Managed Camunda 8. Is this correct? And are there any plans to support multi-tenancy for SaaS in the future?
I am pretty sure the task ID is unique across all tenants, but this is a good question that I don’t have a complete answer for! I will discuss with the engineering teams and find a solid answer, and also work to update our documentation.
Yes, multi-tenancy is only supported by Self-Managed at this time. SaaS provides a unique set of challenges to solve to support multi-tenancy. There isn’t a target release version/date yet, but it is in development.
Follow up - I spoke with our engineer team, and they confirmed the task ID is unique across tenants. The REST API does support multi-tenancy and requires the appropriate permissions on the API client to complete tasks assigned to a tenant. Future REST endpoints will have tenant options, but as the task ID is unique, these endpoints didn’t have a specific tenant ID parameter. Hope that helps!