Skip to main content
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.
WebAdmin is currently a pre-release (0.8.6-SNAPSHOT) and targets ASEE Flow 1.0.0-beta-6 or later. Artifacts are published to Repsy as pre-release builds.

​
What you get

  • A modern React UI served at /webadmin (the base path is configurable)
  • Four authentication modes out of the box: Basic, Form, OAuth2, and Keycloak
  • A pre-configured security layer wired to the engine’s 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

​
Modules

WebAdmin is a multi-module Maven build:
  • aseeflow-webadmin-spring-boot-starter — the reusable starter that bundles the UI and backend; the main artifact you depend on.
  • aseeflow-webadmin-ui — the React (Vite) frontend, packaged as static assets in a JAR.
  • aseeflow-webadmin-war — WAR packaging for traditional servlet containers (Tomcat, WildFly).
  • aseeflow-webadmin-spring-boot-demo — a demo application showcasing every authentication mode and database option.
  • docker — a Docker Compose setup with Keycloak and PostgreSQL for local development.

​
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 — add WebAdmin to a Spring Boot app in about ten minutes.
  • Configuration — the full property reference.
  • Authentication — choose and configure an authentication mode.
  • Deployment — Spring Boot JAR vs. WAR for Tomcat / WildFly.
  • Docker — run Keycloak and PostgreSQL for local testing.