Current Limitation
relates to #4343
Description
The consent screen includes a flow timer to limit how long a user can spend granting consent. Currently, when the timer elapses, the application fails to handle the timeout properly. Similar to the Deny / Cancel action, timing out should automatically abort the flow and send the user back to the Relying Party (RP) / Client Portal with an appropriate error code.
Expected Behavior
When the consent screen flow timer reaches zero:
- The consent session should automatically terminate.
- The system should trigger a cancellation process (e.g., using a dedicated flow cancellation executor).
- The user should be redirected back to the Relying Party (RP) / Client Portal with a specific timeout/rejection error code.
Current Behavior
Upon timer expiration, the flow does not automatically redirect the user back to the Relying Party portal with the required error payload.
Steps to Reproduce
- Initiate an authentication flow to reach the consent screen.
- Wait for the consent flow timer to elapse completely without clicking any buttons.
- Result: The system fails to trigger the cancellation executor/redirect to the RP portal with the expected error code.
Suggested Improvement
Proposed Solution
Leverage a dedicated cancellation executor (or the same mechanism handling the Deny button) to catch the timer expiration event, terminate the flow, and execute the redirect to the client portal with the designated error payload.
Current Limitation
relates to #4343
Description
The consent screen includes a flow timer to limit how long a user can spend granting consent. Currently, when the timer elapses, the application fails to handle the timeout properly. Similar to the Deny / Cancel action, timing out should automatically abort the flow and send the user back to the Relying Party (RP) / Client Portal with an appropriate error code.
Expected Behavior
When the consent screen flow timer reaches zero:
Current Behavior
Upon timer expiration, the flow does not automatically redirect the user back to the Relying Party portal with the required error payload.
Steps to Reproduce
Suggested Improvement
Proposed Solution
Leverage a dedicated cancellation executor (or the same mechanism handling the Deny button) to catch the timer expiration event, terminate the flow, and execute the redirect to the client portal with the designated error payload.