Making Identity production ready
We recommend considering the following topics when moving Identity into a production environment.
Keycloak dependency​
As Keycloak is an external-based dependency of the Identity application, we recommend looking at Keycloak's documentation on production configuration to make sure your Keycloak instance is production-ready.
Backing up​
To ensure recovery is possible, we recommend regularly backing up the database that supports Keycloak.
Helm deployment​
If you deployed the Camunda platform using our Helm charts, by default there will be a Postgres database deployed with it. In this instance, we recommend reading the Postgres documentation for guidance on backing up.
Alternative deployment​
If your Keycloak service uses a different database provider than Postgres, we recommend referencing the backup section of the documentation for your chosen provider and version.
Enabling TLS​
A safe and healthy exchange of secure data requires Transport Layer Security (TLS).
TLS support for Identity can be enabled by setting configuration values. Visit Spring - Configure SSL for more information.
To enable TLS alongside Keycloak, visit the Keycloak documentation regarding TLS enablement.
Setting Identity URL​
To ensure that the authentication flows are successful, the IDENTITY_URL
should be set to the URL of the Identity service.