FOUR-32466 Octane CRITICAL Data Leaks Between Requests $processRequest

[devmiguelangel]

Issue & Reproduction Steps

Octane CRITICAL Data Leaks Between Requests $processRequest

Solution

• The solution replaces static redirect state with a container-scoped RedirectToEventService.
• All workflow listeners share this service during one HTTP request or queue job. The latest redirect candidate wins, state is cleared before broadcasting, and BpmnAction resets it on every exit path. Octane then discards the scoped service between requests, preventing process-request data from leaking into later operations.

Related Tickets & Packages

FOUR-32466

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube