...
In conclusion, no action is needed for 'system' users, but for common admin users, it's advisable to add 'type='staff''.
Changes for config values
In consortium mode we have only 1 UI available for a central tenant, so properties that are stored in mod-configuration like FOLIO_HOST should be pointed to this single host for every tenant.
BE Modules modified for supporting consortia functionality
...
| № | Module | Changes made | Hosting changes |
|---|
| 1 | mod-consortia | - Tenant management
- User affiliations/shadow users managements
- Share instances
- Share/Edit/Delete any setting
- Implement Publish Coordinator mechanism to perform any multitenant operation
| Make sure that password for consortia system user populated via this env variable: SYSTEM_USER_PASSWORD, OKAPI_URL also should be populated. The full list of env variables is presented in the Readme: https://github.com/folio-org/mod-consortia#environment-variables |
| 2 | mod-users | - Implement sending USER_CRETED, USER_UPDATED, USER_DELETED events when consortia mode is enabled
- Check username uniqueness across tenants
- Add mechanism with /user_tenant to identify is consortia mode enabled and to get central tenant id
- Store info about all users from all consortium tenants in central place with using /user-tenant endpoint
| - |
| 3 | mod-users-bl | - Populate all required user's info from correct tenant after login occurred
- Forgot password/ Forgot username for ECS mode
- Support resetting password for ECS mode
| - |
| 4 | mod-login | - Allow to login by any consortium user into the correct tenant from the central tenant UI
| - |
| 5 | mod-authtoken | - Allow cross tenant requests in ECS mode
- Add suport of RTR in ECS mode
| System param(declared in JAVA_OPTS) should be added: -Dallow.cross.tenant.requests=true | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | RANCHER-903 |
|---|
|
|
...
| № | Module | Changes made | Hosting changes |
|---|
| 1 | mod-search | - Adjust search, browse and stream ids functionalities for lookup across tenants
| Tenant paramenter centralTenantId should be added(during tenant enabling) | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | RANCHER-898 |
|---|
|
|
| 2 | mod-entities-links | - Shadow authorities population, adjustments for shared authorities linking
| - |
...
| № | Issue description | Related tickets |
|---|
| 1 | Simaultainious adding tenants to consortia can cause concurrent issues | | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODCON-73 |
|---|
|
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | RANCHER-893 |
|---|
|
|
...