@bpmnenthusiast and @Mukesh_Reddy - I believe we’ve found the missing configs! It was quite a journey, but a good one for us to take as we’ve identified important gaps in our documentation and default configurations. Thanks for the patience and the feedback!
Add these variables to the Zeebe configuration in docker-compose.yaml:
- CAMUNDA_IDENTITY_ISSUERBACKENDURL=http://keycloak:8080/auth/realms/camunda-platform
- CAMUNDA_IDENTITY_BASEURL=http://identity:8084
- CAMUNDA_IDENTITY_AUDIENCE=zeebe-api
- SPRING_PROFILES_ACTIVE=identity-auth
I think these can replace some of the variables, but I am not totally sure, so best leave the other configuration values as is for now.
Let me know if this works for you!
opened 01:30PM - 31 Jul 24 UTC
kind/toil
component/zeebe
<!--
In case you have questions about our software we encourage everyone to par… ticipate in our community via the
- Camunda Platform community forum https://forum.camunda.io/ or
- Slack https://camunda-cloud.slack.com/ (For invite: https://camunda-slack-invite.herokuapp.com/)
There you can exchange ideas with other Zeebe and Camunda Platform 8 users, as well as the product developers, and use the search to find answer to similar questions.
This issue template is used by the Zeebe engineers to create general tasks.
-->
**Description**
A customer was trying to use Multi-tenancy with Zeebe User Tasks and were getting 404 when trying to assing or complete tasks using Zeebe API (customer used camunda-platform to spin-up the environment).
After investigation we found out that the we had some missing configurations:
```
- CAMUNDA_IDENTITY_ISSUERBACKENDURL=http://keycloak:8080/auth/realms/camunda-platform
- CAMUNDA_IDENTITY_BASEURL=http://identity:8084
- CAMUNDA_IDENTITY_AUDIENCE=zeebe-api
- SPRING_PROFILES_ACTIVE=identity-auth
```
We probably should add those extra configurations to documentation and camunda-platform to avoid confusion in the future.