> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aseeflow.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Web applications

To enable the [Web Applications](/webapps) you can use the following starter in your `pom.xml`:

```xml theme={null}
<dependency>
  <groupId>org.aseeflow.bpm.springboot</groupId>
  <artifactId>aseeflow-bpm-spring-boot-starter-webapp</artifactId>
  <version>1.0.0</version>
</dependency>
```

By default the application path is `/camunda`, so without any further configuration you can access
the Webapps under [http://localhost:8080/camunda/app/](http://localhost:8080/camunda/app/).

### Configurations

You can change the application path with the following configuration property in your `application.yaml` file:

```properties theme={null}
camunda.bpm.webapp.application-path=/my/application/path
```

By default, the starter registers a controller to redirect `/` to ASEE Flow's bundled `index.html`.
To disable this, you have to add to your application properties:

```properties theme={null}
camunda.bpm.webapp.index-redirect-enabled=false
```

### Error Pages

The default error handling coming with the Spring Boot ('whitelabel' error page) is enabled in the starter. To switch to the ASEE Flow error pages (`webjar/META-INF/resources/webjars/camunda/error-XYZ-page.html`), please put them to the application folder structure under `/src/main/resources/public/error/XYZ.html`.

### Building Custom REST APIs

The ASEE Flow Web Applications use a `CSRF Prevention Filter` that expects a `CSRF Token` on any
modifying request for paths beginning with `/camunda/api/` or `/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 `camunda.bpm.webapp.csrf.entry-points`).