FOUR-16704: Session Token Not Invalidated on Logout

[danloa]

Issue & Reproduction Steps

Follow the instructions in the video "Screen Recording on 2024-12-03 at 12-00-33.mp4" of the ticket https://processmaker.atlassian.net/browse/FOUR-16704

Solution

• Cache de status of logged in/logged out of a user
  

Related Tickets & Packages

https://processmaker.atlassian.net/browse/FOUR-16704

Tests done:

• Login/logout in one device --> OK
• Login/logout in multiple devices --> OK
• Socialite authentication (used SAML) --> OK
• Endpoint called using Postman or similar -> OK

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.

ci:deploy

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube