Set tenant context based on authentication response (Eureka, ECS - Single tenant UX)

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 the overrideUser=true query parameter returns originalTenantId. Use this value when creating a session on the UI. But when changing affiliation, the overrideUser 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.