> ## 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.

# ASEE Flow WebAdmin

ASEE Flow WebAdmin is a modern, React-based administrative interface for ASEE Flow applications. You add it to a Spring Boot application as a starter dependency, and the UI becomes available at `/webadmin` with a pre-configured security layer that integrates with the ASEE Flow engine's Identity Service.

<Info>
  WebAdmin is evolving rapidly. Since 1.0.2 it is released together with ASEE Flow and has the same version number: WebAdmin 1.0.2 belongs to ASEE Flow 1.0.2. Artifacts are available to ASEE Flow customers (see [Accessing artifacts](/introduction/downloading-aseeflow#accessing-artifacts)).
</Info>

## Why WebAdmin?

Camunda 7 Community Edition reached [end of life](https://forum.camunda.io/t/important-update-camunda-7-community-edition-end-of-life-announced/50921) with its final release, 7.24, on 14 October 2025 — upstream publishes no further releases or security patches.

ASEE Flow forks that engine and **continues to provide security patches** for it.

The bundled web apps are a different matter. Cockpit, Tasklist, and Admin are built on **AngularJS 1.x**, which Google declared [end of life in December 2021](https://docs.angularjs.org/misc/version-support-status).
Camunda's own mitigation was to move the apps onto a [third-party-maintained AngularJS fork](https://camunda.com/blog/2022/02/ensuring-continuous-support-of-angularjs-in-camunda-platform-7-17/) — life support, not modernization.
Keeping a large, unsupported front-end framework secure over the long term isn't practical, so **ASEE Flow ships the legacy web apps as-is** and invests instead in WebAdmin, a modern React UI that is actively maintained.

**Use WebAdmin for day-to-day administration.** The legacy web apps remain available for compatibility but are not actively maintained.

## What you get

* A modern React UI served at `/webadmin` (the base path is configurable)
* Four authentication modes out of the box: [Basic](/webadmin/authentication/basic), [Form](/webadmin/authentication/form), [OAuth2](/webadmin/authentication/oauth2), and [Keycloak](/webadmin/authentication/keycloak)
* A pre-configured security layer wired to the engine's [Identity Service](/user-guide/process-engine/identity-service)
* An optional Engine REST proxy for same-origin requests and OAuth2 token forwarding
* Swagger UI integration and configurable links to the legacy web apps (Cockpit, Tasklist, Admin)
* Deployment as a Spring Boot JAR or as a WAR for external Tomcat / WildFly

## A consistent interface

WebAdmin brings the areas the legacy web apps split across Cockpit, Tasklist, and Admin into a single console. Every area in the left-hand menu — processes, tasks, decisions, variables, incidents, jobs, deployments, batches, and admin — follows the **same pattern**: a sortable table, basic and advanced filtering, and a focused detail view for the selected item.

The screens below show **process definitions** as an example of that pattern. The same layout and interactions apply across every area — they are an illustration of the experience, not a complete reference of WebAdmin's features.

A sortable **table view** of the area's entries:

<img src="https://mintcdn.com/aseeflow/XcfAnMg02VEHMjeO/webadmin/img/processDefinitionsView.png?fit=max&auto=format&n=XcfAnMg02VEHMjeO&q=85&s=1710649c45ca33c1a779b8fd173358b7" alt="WebAdmin process definitions — table view" width="1604" height="906" data-path="webadmin/img/processDefinitionsView.png" />

A **basic filter** over the common fields:

<img src="https://mintcdn.com/aseeflow/XcfAnMg02VEHMjeO/webadmin/img/processDefinitionsBasicFilter.png?fit=max&auto=format&n=XcfAnMg02VEHMjeO&q=85&s=a66884f9bf5be8bf28b142218fe038c7" alt="WebAdmin process definitions — basic filter" width="1600" height="999" data-path="webadmin/img/processDefinitionsBasicFilter.png" />

An **advanced filter** for multi-criteria queries over all fields the engine REST API exposes:

<img src="https://mintcdn.com/aseeflow/XcfAnMg02VEHMjeO/webadmin/img/processDefinitionsAdvancedFilter.png?fit=max&auto=format&n=XcfAnMg02VEHMjeO&q=85&s=5e0d0272996b7524f43a08a63b7f5cc6" alt="WebAdmin process definitions — advanced filter" width="1599" height="1060" data-path="webadmin/img/processDefinitionsAdvancedFilter.png" />

A focused **detail view** of a single entity:

<img src="https://mintcdn.com/aseeflow/XcfAnMg02VEHMjeO/webadmin/img/processDefinitionsDetailsView.png?fit=max&auto=format&n=XcfAnMg02VEHMjeO&q=85&s=5e95e9e11f3a012c1a29d1853cf9e2aa" alt="WebAdmin process definitions — detail view" width="1596" height="992" data-path="webadmin/img/processDefinitionsDetailsView.png" />

## How it relates to ASEE Flow

WebAdmin builds on the ASEE Flow Spring Boot starters (`aseeflow-bpm-spring-boot-starter-webapp`, `-rest`, and `-security`). It consumes the engine's REST API for all operations and bridges the engine's Identity Service to your chosen authentication provider — including an optional Keycloak identity provider plugin for user and group synchronization.

## Next steps

* [Quick start](/webadmin/quick-start) — add WebAdmin to a Spring Boot app in about ten minutes.
* [Configuration](/webadmin/configuration) — the full property reference.
* [Authentication](/webadmin/authentication) — choose and configure an authentication mode.
* [Deployment](/webadmin/deployment) — Spring Boot JAR vs. WAR for Tomcat / WildFly.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.