2027720 - Force sign out: does not apply to client and results in multiple session being listed in console

Status: VERIFIED FIXED

(Enterprise Products :: Console, defect)

Description

[Miruna Curtean]

Attachment: session multiply when using Force sign out.png

Found in

stage console>user page

Affected environment

Staging

Tested platforms

All platforms: macOS Tahoe 26.3, Win 11, Ubuntu 24.0

Preconditions
Admin access to stage console.
Make sure there is only 1 device listed in User's profile> Devices & browsers.

Steps to reproduce

1. Navigate to a different user than admin, in User>Devices & browsers
2. Click Force Sign out and observe the results in console and in client.

Expected result
OS device and browser session is terminated in console and no removed from the Devices & browsers section.
User is logged out from their firefox instance (no windows remain open)

Actual result
Client:
Force Sign out does not actually sign out:

• a user on another device
• the admin user on another device
• the admin user from the very same session they are logged in with the console

Console
When a user signs out or is forced to sign out with no remaining sessions, the Device and browsers list is populated with "Signed out"duplicate sessions.

Note: Trying to restart the browser after it has been forced signed out from the console will result not work. The process needs to be terminated in from a task manager in order to be able to open the client again.

Comment 1

[Julien Wajsberg [:julienw]]

Note: Trying to restart the browser after it has been forced signed out from the console will result not work. The process needs to be terminated in from a task manager in order to be able to open the client again.

This part is I believe a separate bug, would you please file another bug on the Client for that?

Also can you please precise what "Force Sign out" button you're using, is that the one next to a session, or the one at the page bottom?
Thank you

Comment 2

[Julien Wajsberg [:julienw]]

(In reply to Julien Wajsberg [:julienw] from comment #1)

Note: Trying to restart the browser after it has been forced signed out from the console will result not work. The process needs to be terminated in from a task manager in order to be able to open the client again.

This part is I believe a separate bug, would you please file another bug on the Client for that?

Seems to be https://github.com/mozilla/enterprise-firefox/pull/550

Comment 3

[Miruna Curtean]

(In reply to Julien Wajsberg [:julienw] from comment #1)

Note: Trying to restart the browser after it has been forced signed out from the console will result not work. The process needs to be terminated in from a task manager in order to be able to open the client again.

This part is I believe a separate bug, would you please file another bug on the Client for that?

Also can you please precise what "Force Sign out" button you're using, is that the one next to a session, or the one at the page bottom?
Thank you

I have added the bug for restart after force sign out - FxE client restart does not work and process needs to be terminated in order to launch Felt screen again after Force Sign out, with the disclaimer this might not be a valid use case after Force Sign out is actually working, since it will sign out the user, so it will be impossible to actually restart, but at least the part of launching FxE again should work without having to terminate the process again.
As for the Force Sign out button, it's the one next to the session that I mostly used, but the same behavior occurs when using the one at the bottom of the page, which signs out the user from all sessions.

Comment 4

[Julien Wajsberg [:julienw]]

Attachment: GitHub Pull Request

Comment 5

[Miruna Curtean]

Verified fixed on 151.0a1 (20260403052206) with macOS Tahoe 26.3 and Win 11 and Ubuntu 24.0 and Force sign out is working as expected, and the Felt screen is launched after forced sign out with an appropriate banner informing the user of the action. .

Comment 6

[Julien Wajsberg [:julienw]]

Miruna, could you also please check they the behavior in the web console is more appropriate, regarding the sessions list?
Thank you

Comment 7

[Miruna Curtean]

Attachment: Force sign out multiple sessions.gif

You're right, I missed this aspect, it was a chaotic week; thank you for checking.
Retested it on 151.0a1 (Build ID: 20260403052206) and the Apr 3, 2026, 11:15 PM stage console and I evidently has multiple sessions from the previous week's testing, but no new ones were generated when I forcefully signed out my account from macOS.
Since the multiple sessions from last week are still there, I propose we wait until they are gone to re-test and make sure no new sessions are generated and if that is the case, re-open the bug.

Comment 8

[Julien Wajsberg [:julienw]]

Hey Miruna

Since the multiple sessions from last week are still there, I propose we wait until they are gone to re-test and make sure no new sessions are generated and if that is the case, re-open the bug.

They won't likely go away.

The way things work now is that, in this view, we display one session for a device.

But to identify a device, we use a device id. This device id is stored in the firefox profile. Therefore if you delete the firefox profile, a new device id will be attributed, and therefore everything happens as if a new device has been logged in for this user. And therefore these sessions will still be visible in the list.

What I notice in your image though, is that they should probably be ordered by "last seen". I'll see e if we can do that easily.

Thank you!