2038135 - Fine tune the UX around the flow of expired refresh tokens and being signed out forcefully

Status: NEW

(Enterprise Products :: Firefox, task)

Description

[Andi Pieper]

Attachment: User has been forcefully signed out via the admin console.

During review of bug 2025534 an issue was raised that was outside the scope of the bug. There are still some differences between the figma designs around the Felt info/error boxes that are shown in different scenarios. Currently, if the user logs out actively by pressing the enterprise signout button, the browser quits and the Felt email dialog is shown - exactly what the user is expecting, no additional information needed.

If the user is forcefully signed out via the admin console, the browser is closing for the user without warning (which is what is needed at that point) and the Felt window comes up wit the message in the attached screenshot.

This is somewhat different to what is in the figma UI design document, where there are multiple different messages around signouts. I think it would be helpful to review the figma document and the current status of Enterprise Firefox to come to a proper solution and then implement the necessary wiring in Felt/Firefox.

Comment 1

[Andi Pieper]

I have implemented the above screen, with a generic info message that the user has been signed out, either due to inactivity or forceful signout by the console admin. :mcroud can you give an approval for this solution before we dive into optimizing the user flow.

Comment 2

[Enterprise UX]

Thank you for explaining, Andi.
Until we are able to provide dedicated messaging for admin-lead sign outs and server errors, I'm fine with this catch-all messaging to inform the user what just happened. Thanks!

Comment 3

[:gerard-majax]

(In reply to Enterprise UX from comment #2)

Thank you for explaining, Andi.
Until we are able to provide dedicated messaging for admin-lead sign outs and server errors, I'm fine with this catch-all messaging to inform the user what just happened. Thanks!

While this is currently true, it was the result of the changes landed recently to handle Felt-side token refresh. The information was there before.

Too generic error message are problematic when having to debug what happens in production, we should fix this as soon as possible