Versions Compared

Old Version 60

changes.mady.by.user Serhii_Nosko

Saved on

compared with

New Version Current

changes.mady.by.user Serhii_Nosko

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Warning
titleDifferences between central and institutional tenants

Module folio_consortia-settings should be enabled only in consortium central tenant

Configure tenants

  • Reference data & sample data should NOT be created on both central and institutional tenants

...

  • .
Warning

Existing settings in a tenant cannot be shared via Consortium Manager. Settings have to be created via Consortium Manager to be shareable.

  • Reset password link, SMTP for sending emails should be configured on all tenants. Separate admin users in each tenant can be created to apply all this configuration.

...


Create admin user in the central tenant

...

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

...

№ModuleChanges madeHosting changes
1mod-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:  SYSTEMSYSTEM_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

2mod-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
-
3mod-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
-
4mod-login
  • Allow to login by any consortium user into the correct tenant from the central tenant UI
-
5mod-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
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-903

...

№ModuleChanges madeHosting changes
1mod-search
  • Adjust search, browse and stream ids functionalities for lookup across tenants

Tenant paramenter centralTenantId should be added(during tenant enabling)

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-898

2mod-entities-links
  • Shadow authorities population, adjustments for shared authorities linking
-

...

№Issue descriptionRelated tickets
1Simaultainious adding tenants to consortia can cause concurrent issues

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODCON-73

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-893

...