...
- Tenant admin details are saved by default into an internal H2 database. This is configurable to point to an external database if preferred. This can then be scaled appropriately. The tenants can have their own multiple directories set up and these configurations can be dynamically configured via the Management Console.
- The super admin or tenant admin can add user stores through the UI, to their own domain. We have allowed dynamic configurations Dynamic configurations are possible only for secondary user stores and the 'Primaryprimary' user store is not configurable at run time. This was because it is is because primary user stores are available for all tenants and allowing changes to it's the configuration at run time can guide lead to instability of the system. With this limitation we have been able to keep the design simple and avoid some crucial run time complexities that may have occurred. (eg: Primary user store keeps super admin data used to sign in and if super admin himself changes the configuration of Primary user store, the status of the system in between, is not stable.) So the Primary So the primary user store is treated as a static property in the implementation that is a basic requirement and must be configured prior to run the system properlytime.
| Info | ||
|---|---|---|
When multitenancy is enabled and a tenant becomes inactive for a long period of time, the tenant is unloaded from the server's memory. By default, the time period is 30 minutes. After that, the tenant has to log in again before sending requests to the server. You change the default time period allowed for tenant inactiveness by adding
|