Skip to content
~/ Yusif Mustafa
All case studies

Avrora Group

Keycloak Auth & Camunda Workflow Integration

OIDC login flows, session handling and role-based access control, plus live business-process stages from Camunda, across microservice-based platforms.

Role
Frontend Developer
Period
Jul 2026 – Present
  • Keycloak
  • OIDC / OAuth 2.0
  • RBAC
  • Camunda BPM
  • Microservices
  • TypeScript

Context

Avrora Group builds several microservice-based enterprise platforms. Each one needs secure sign-in, role-aware interfaces, and visibility into long-running business processes. TODO: name the product type (without confidential details) and its users.

Problem

  • Users must authenticate once and get the right access across independent services.
  • The UI must show only what each role is allowed to do.
  • Business processes run in a workflow engine, but users need to see the current stage in the interface.

My role

  • Implemented authentication and authorization with Keycloak (OpenID Connect / OAuth 2.0): login flows and session handling.
  • Implemented role-based access control (RBAC) across routes and UI components.
  • Integrated the Camunda workflow engine to track and display the current stage of business processes.
  • Worked with backend teams to integrate REST APIs exposed by independent microservices.

Solution

Authentication & authorization

React / Angular app

route + UI guards

1 · redirect

Keycloak

OIDC / OAuth 2.0

2 · tokens

Microservices

REST · role checks

Business process tracking

Microservice

starts / advances process

3 · state

Camunda

workflow engine

4 · stage

UI

current stage shown

Simplified flow: the app signs users in through Keycloak, calls services with the issued tokens, and displays the process stage reported from Camunda.
  • Login and session: the app redirects to Keycloak using the OIDC flow, receives tokens and keeps the session alive by refreshing them. TODO: confirm the exact flow (authorization code + PKCE) and refresh strategy.
  • RBAC: roles from the token drive route guards and UI-level checks, so unauthorized screens and actions are hidden and blocked.
  • Process tracking: the UI reads the current process state from Camunda through the backend and shows it as a stage indicator.
  • TODO: add key decisions (token storage, handling expired sessions, polling vs. events).

Result

  • A single, consistent sign-in and permission model reused across projects.
  • Users see where their process stands without asking.
  • TODO: add numbers (projects using it, reduced support requests, time saved).