Access types that are already stored in DB have to be associated with KB credentials moved from mod-configuration module to mod-kb-ebsco-java. Association should be done by storing a reference to KB credentials in access_type table:
- credentialsId field populated with primary key of the KB credentials
More details on DB schema changes can be found in the dedicated section of "Spike: MODKBEKBJ-390 - describe design for "Single tenant multiple EBSCO KBs" scenario"
- existing access types associated with single KB credentials that have been preconfigured before the update
- DB script that does the migration should be provided
- types that have been present are associated with preexisting credentials once the script is applied