Skip to main content
This guide provides a comprehensive reference for configuring the FlowX Admin microservice using environment variables and configuration files.

Infrastructure Prerequisites

Before setting up the Admin microservice, ensure the following components are properly set up:
  • Database Instance: The Admin microservice connects to the same database as the FlowX.AI Engine.
  • MongoDB: For additional data management.
  • Redis: For caching and transient data storage.
  • Kafka: For audit logs, events, and messaging (if using FlowX.AI Audit functionality).

Core configuration

Server configuration

Database configuration

The Admin microservice connects to the same PostgreSQL or Oracle database as the FlowX.AI Engine for storing process definitions.
You will need to make sure that the user, password, connection link and database name are configured correctly, otherwise, you will receive errors at start time.
The database schema is managed by a Liquibase script provided with the Engine.

MongoDB configuration

The Admin microservice also connects to a MongoDB database instance for additional data management.
Ensure that the MongoDB configuration is compatible with the same database requirements as the FlowX.AI Engine, especially if sharing database instances.

Redis and caching configuration

Redis is used for caching and storing transient data.
The SPRING_REDIS_* variables are deprecated and will be removed in a future FlowX version. Please use the corresponding SPRING_DATA_REDIS_* variables instead.

Kafka configuration

The Admin microservice uses Kafka for sending audit logs, managing scheduled timer events, platform component versions, and start timer event updates.

General Kafka settings

Kafka producer configuration

Kafka consumer configuration

Topic naming configuration

Kafka topics configuration

Audit topics

Platform Topics

Events gateway topics

Build topics

Resource topics

OAuth authentication for Kafka

When using the kafka-auth profile, the following variables configure OAuth for Kafka:
When using the kafka-auth profile, the security protocol will automatically be set to SASL_PLAINTEXT and the SASL mechanism will be set to OAUTHBEARER.

Logging configuration

The FlowX Admin microservice provides granular control over logging levels for different components:

Localization settings

Health monitoring

Platform health configuration

Multi-edit and undo/redo configuration

Resources usage configuration

Authentication and Authorization Configuration

The FlowX Admin microservice supports authentication and authorization through OpenID Connect (with Keycloak as the default provider) and allows detailed role-based access control.

OpenID Connect Configuration

Service Account Configuration

The following service account configuration is deprecated but still supported for backward compatibility.

Spring Security OAuth2 Client Configuration

Identity Provider Configuration

Keycloak Configuration

Microsoft Entra ID configuration

The role-based access control is configured in the application YAML and grants specific permissions for platform management, user management, process management, integrations management, and configuration management.
In production environments, never use the default service account credentials. Always configure secure, environment-specific credentials for authentication.
Sensitive information such as passwords and client secrets should be managed securely using environment variables or a secrets management solution in production environments.
Last modified on September 19, 2025