I’m integrating Camunda Identity with an external Keycloak instance, where I already have a custom realm (qportal) configured with all necessary resources. My environment includes:
IDENTITY_KEYCLOAK_REALM=qportal
IDENTITY_KEYCLOAK_CREATE_REALM=false
CAMUNDA_IDENTITY_TYPE=KEYCLOAK
IDENTITY_AUTH_PROVIDER_ISSUER_URL=https://keycloak-dev.att/keycloak/realms/qportal
IDENTITY_AUTH_PROVIDER_BACKEND_URL=https://keycloak-dev.att/keycloak/realms/qportal
IDENTITY_AUTH_PROVIDER_CLIENT_ID=camunda-identity
IDENTITY_AUTH_PROVIDER_CLIENT_SECRET=client-secret
Despite these settings, Identity still attempts to use the default realm camunda-platform. If I pre-create the camunda-identity client in qportal, Identity throws a 409 Conflict. If I remove the client, I get a 401 Unauthorized, indicating it may not actually be pointing to qportal as expected.
Reviewing the container setup, it seems the realm creation logic is hard-coded into the identity.jar. Is there any official way to prevent Identity from auto-creating the default realm and resources, and ensure it strictly uses the external realm I provide?