Set tenant context based on authentication response (Eureka, ECS - Single tenant UX)
Description
Environment
None
Potential Workaround
None
Attachments
2
Checklist
hideActivity
Show:

Yury Barsukou 5 days agoEdited
Tested on https://folio-etesting-snapshot-consortium.ci.folio.org, looks fine
Details
Details
Assignee

Reporter

Labels
Priority
Story Points
3
Development Team
Eureka
Release
Sunflower (R1 2025)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created February 13, 2025 at 1:59 PM
Updated 5 days ago
TestRail: Cases
TestRail: Runs
Overview:
In (Option #4), there’s one step which is not explicitly mentioned. This is the sole place in this solution which requires work in the UI. An authentication response is returned from keycloak, and the user is taken to the Folio landing page. However, stripes needs to inspect the response in order to determine the tenant context, so it can use it to populate
x-okapi-tenant
when making calls to the backend.Backend side story -
Scope:
Inspect the authentication response from Keycloak and set the tenant context in stripes.
The
_self
endpoint with theoverrideUser=true
query parameter returnsoriginalTenantId
. Use this value when creating a session on the UI. But when changing affiliation, theoverrideUser
parameter should not be used.NOTE: Coordination with the BE devs working on this feature is required. They should be able to provide additional details.
Preconditions:
Env is in consortia mode;
Create user which should be affiliated with member tenant;
Acceptance Criteria:
on login _self endpoint is called with
overrideUser=true
parameter, correct member tenant is settled to the navigation bar.On change affiliation _self endpoint is called without
overrideUser
, selected tenant is settled to the navigation bar.