When we build the app with Spring Boot, Camunda resources are mapped on /app, /api and /lib.
There must be a possibility to put the resources under another context. E.g. /camunda/api, /camunda/app etc.

Ideally, this "camunda" context path must be configurable.

Implementation hints:
Most probably Spring Boot packages all web resources together under one context, when deploying them on embedded Tomcat. We could research, if its possible to separate them somehow.

Issue originated from here: https://github.com/camunda/camunda-bpm-spring-boot-starter/issues/150