We need a tenant resolver strategy that is based on a selection screen.
After logging in the user has to select a tenant.
The tenant selection should populate its list from a configurable endpoint that returns the shape:
{
«id»: «some string»,
«name»: «some string»
}The UI should render the list with names.
The page needs to be like other pages, overridable / replaceable.
The page will not call the endpoint itself, but instead be able to get the tenants from a cookie, in the same way the identity provider selection page works.
Once selected we need to produce a cookie from the backend that holds the tenantId, on subsequent requests we will look for this cookie and use it as tenantId.
We will need specs and documentation for this approach, including how to build a page.
We need a tenant resolver strategy that is based on a selection screen.
After logging in the user has to select a tenant.
The tenant selection should populate its list from a configurable endpoint that returns the shape:
{ «id»: «some string», «name»: «some string» }The UI should render the list with names.
The page needs to be like other pages, overridable / replaceable.
The page will not call the endpoint itself, but instead be able to get the tenants from a cookie, in the same way the identity provider selection page works.
Once selected we need to produce a cookie from the backend that holds the tenantId, on subsequent requests we will look for this cookie and use it as tenantId.
We will need specs and documentation for this approach, including how to build a page.