Issues with Multi-Tenancy Configuration in Camunda 8 Self-Managed

Camunda 8 Topics Discussion & Questions
,
1

I’m encountering issues while trying to enable multi-tenancy in Camunda 8 Self-Managed. I used the official docker compose setup , which worked fine initially. However, after simply setting the parameter MULTI_TENANCY_ENABLED=true and restarting all services without any other changes, the connectors service is repeatedly throwing errors for various external connections:

2024-10-04 07:41:21 2024-10-03T23:41:21.845Z  WARN 1 --- [ult-executor-28] io.camunda.zeebe.client.job.poller       : Failed to activate jobs for worker RabbitMQ Producer and job type io.camunda:connector-rabbitmq:1
2024-10-04 07:41:21 
2024-10-04 07:41:21 io.grpc.StatusRuntimeException: INVALID_ARGUMENT: Expected to handle gRPC request ActivateJobs with tenant identifier '<default>', but tenant could not be retrieved from the request context
2024-10-04 07:41:21     at io.grpc.Status.asRuntimeException(Status.java:533)
2024-10-04 07:41:21     at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:481)
2024-10-04 07:41:21     at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:564)
2024-10-04 07:41:21     at io.grpc.internal.ClientCallImpl.access$100(ClientCallImpl.java:72)
2024-10-04 07:41:21     at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:729)
2024-10-04 07:41:21     at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:710)
2024-10-04 07:41:21     at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
2024-10-04 07:41:21     at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:133)
2024-10-04 07:41:21     at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
2024-10-04 07:41:21     at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
2024-10-04 07:41:21     at java.base/java.lang.Thread.run(Unknown Source)

Could you please help me resolve this issue?

2

Hi @cooperlyt , that sounds frustrating. Let’s see if I can help!

Did you see this guide to enable multi-tenancy?

It looks like the other services (e.g., Zeebe) might not have multi-tenenacy enabled.

Let us know if this helps :smile:

3

It’s my fault; I overlooked the comments in the environment variables:

# This requires use of identity for authentication
#
# ZEEBE_AUTHENTICATION_MODE=identity
#
4

I would like to ask about identity management in a multi-tenant setup.

Does Camunda support using different realms from the same Keycloak instance for different tenants? For example, having TenantA use realmA, and TenantB use realmB.