Identity still tries to create the dev-camunda-platform realm instead of using our external realm (dev-camunda-platform)

[zee-bot]

Summary

The issue you’re experiencing is a known limitation in Camunda Identity 8.8. Here are the key points:

The Problem

• Camunda Identity always attempts to bootstrap/create realm resources during startup, even when configured to use an external Keycloak realm
• This causes “Conflict detected” errors when those resources already exist in your external Keycloak
• Your configuration with KEYCLOAK_REALM: "dev-camunda-platform" and matching CAMUNDA_IDENTITY_ISSUER_URL is correct

Current Status

• No supported workaround exists to disable the automatic realm creation behavior
• Variables like IDENTITY_KEYCLOAK_CREATE_REALM=false are not recognized by Identity
• The bootstrap logic appears to be hard-coded in Identity’s startup process

Next Steps

Since this is a product limitation rather than a configuration issue:

1. Monitor future releases for improvements to this behavior
2. Contact Camunda Support if this is blocking your deployment
3. Consider filing a feature request on the Camunda roadmap if one doesn’t already exist

References

• Connect to an existing Keycloak instance documentation
• Related forum discussion

Your configuration is correct - this is simply a current limitation of the product that the Camunda team may address in future releases.