Done
Details
Assignee
Roman BarannykRoman BarannykReporter
Alexander KurashAlexander KurashLabels
Priority
P2Story Points
3Sprint
NoneDevelopment Team
VegaFix versions
Release
Ramsons (R2 2024)TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Roman Barannyk
Roman BarannykReporter
Alexander Kurash
Alexander KurashLabels
Priority
Story Points
3
Sprint
None
Development Team
Vega
Fix versions
Release
Ramsons (R2 2024)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created September 2, 2024 at 1:47 PM
Updated November 30, 2024 at 4:45 PM
Resolved November 25, 2024 at 2:33 PM
mod-tlr
needs to be able to synchronize users between tenants in a multi-tenant ECS environment. It needs to consume and handle userupdate
events.Consume user
update
event only published by the central tenant, ignore events published by data tenants to avoid an endless loop. In order to determine which tenant is central, make a call toGET /user-tenants?limit=1
and cacheconsortiumId
(this is needed for step 2) andcentralTenantId
(that’s central tenant). This logic was already implemented in .Using
consortiumId
from the previous step, callGET /consortia/{consortiumId}/tenants
to get a list of all tenants of the current consortium.Using a system user, update all of the users in all tenants except central (again, to avoid an endless loop).