To enable the Web Applications you can use the following starter in your
By default the application path is
/camunda, so without any further configuration you can access
the Webapps under http://localhost:8080/camunda/app/.
Please note that this feature is only included in the enterprise edition of the Camunda Platform, it is not available in the community edition.
To use the enterprise Web applications, include another starter:
Also don’t forget to define the appropriate Camunda engine version (with “ee” suffix): see Using Enterprise Edition.
If you are using the enterprise edition, you can also use the
property to provide a license file that is inserted on application start. Or copy your license file under the name
camunda-license.txt to your
src/main/resources. See the dedicated License docs section
for more details on how to add a License key to your Camunda installation.
You can change the application path with the following configuration property in your
By default, the starter registers a controller to redirect
/ to Camunda’s bundled
To disable this, you have to add to your application properties:
The default error handling coming with the Spring Boot (‘whitelabel’ error page) is enabled in the starter. To switch to the Camunda error pages (
webjar/META-INF/resources/webjars/camunda/error-XYZ-page.html), please put them to the application folder structure under
Building Custom REST APIs
The Camunda Web Applications use a
CSRF Prevention Filter that expects a
CSRF Token on any
modifying request for paths beginning with
/camunda/app/. Any modifying requests
mapped to these paths will fail, and the current session will be ended if no CSRF Token is present.
You can avoid this by registering your resources on different paths or add your resources to the
CSRF Prevention Filter Whitelist (via the configuration property