Before
An administrator would likely review the request, determine whether the user's sessions should be force-expired, and manually update the user's account settings. They would then perform a separate session-expiration action and verify that both steps were completed for the same user.
How it works
- Receives the user context and force-expiration request.
- Evaluates whether the request should proceed through the expiration path.
- Applies the next-login password reset action and then expires the user's session cookies.
Workflow details
- Trigger and context: The workflow starts when a trigger provides information about a user and whether that user's sessions should be force-expired.
- Automated decision: It evaluates the force-expiration condition before taking account action, ensuring the downstream steps run only on the selected path.
- Account control: When the condition is met, the workflow applies the configured user action to require a password reset at the next login.
- Session termination: It then performs the session-cookie expiration step for the same user, helping remove existing session access as part of the forced-expiration process.
What changed
The expiration decision and two related user-account actions now run as one triggered sequence for the identified user, instead of requiring separate manual updates and handoffs.
Work removed
Manually reviewing the force-expiration request, updating the user's next-login password requirement, initiating session-cookie expiration, and coordinating the sequence of those account actions.
Expected outcome
At least two recurring manual account-management actions are removed for each qualifying request, with the user password-reset and session-expiration steps handled in a consistent sequence.
