ECS Environment: System log out --> then user log-in should return user to an accurate context.
Description
Potential Workaround
Attachments
- 24 Sep 2024, 12:59 PM
defines
is blocked by
Checklist
hideActivity

Dennis Bridges January 28, 2025 at 9:48 PM
Thanks I agree that this is a new story and I have assigned it to Trillium as it is a P3 and we will need time to define an appropriate solution.

Mikita Siadykh January 28, 2025 at 6:56 PM
@Dennis Bridges actually we didn’t have requirements in this area, especially when RRT was introduced and users started to have shorter sessions instead of tokens without expiration
I would convert it to a story with clear requirements how it should behave - especially talking about “User returns to previously selected affiliation“ - I don’t think there is a good way to implement a login directly to an affiliation user was during log out
cc @Khalilah Gambrell

Khalilah Gambrell January 6, 2025 at 4:33 PM
Assigning to Thunderjet since there is no ECS specific team.

Khalilah Gambrell December 2, 2024 at 4:26 PM
Blocked until Khalilah speaks with POs. cc: @Magda Zacharska
Zak Burke October 28, 2024 at 4:54 PM
https://folio-org.atlassian.net/browse/STCOR-882 consolidates logout functionality into a single component. I’d like to get that work merged first, and then handle this on top of it.
Details
Details
Assignee
Reporter

Overview:
On ECS environment when User is doing bulk edit for a long time in one tenant, logged out from the application and then logged in to another tenant - the job seems to be running but on DevTools error is reported “BulkOperation was not found by id“
After User switches affiliation to the tenant from which they were logged out - bulk operation job continues to run successfully
Steps to Reproduce:
Log into FOLIO as User (created in Central tenant) with the following permissions in Central, Member tenants: Bulk Edit: In app - Edit inventory records, Inventory: All permissions
Switch affiliation to Member tenant
Go to “Bulk edit“ app
Select “Inventory-instances“ record type
Select “Instance UUIDs“ record identifier
Click “or choose file“ button => Upload file with ~100.000 valid Instance UUIDs
Wait until user is logged out from FOLIO (by system not by user)
Log into FOLIO
Expected Results:
User is logged into Member tenant, bulk edit job is running successfully.
User returns to previously selected affiliation (which might not be primary affiliation) and page. And if easier, apply this when user logs out.
OR take user to default FOLIO Landing page
Actual Results:
User is logged into Central tenant, bulk edit job seems to be running but on DevTools error is reported “BulkOperation was not found by id.“ It gives the wrong context as it shows the Bulk-edit page but not in the right tenant. It is misleading to the user.