Uploaded image for project: 'mod-kb-ebsco-java'
  1. mod-kb-ebsco-java
  2. MODKBEKBJ-432

Modify configuration routine to support user related KB credentials

    XMLWordPrintable

Details

    • eHoldings Sprint 87, eHoldings Sprint 88
    • 5
    • Spitfire

    Description

      Endpoints call HoldingsIQ services (EBSCO KB) to get or update records. Each call has to be preconfigured with valid EBSCO knowledgebase credentials. There is only one credential set available at the moment. But it has to be changed to support multiple sets and a set can be associated with a user. This requires changes in the configuration routine of endpoints so that the appropriate KB credentials could be selected from several options depending on the current user.

      More details can be found in the dedicated section of "Spike: MODKBEKBJ-390 - describe design for "Single tenant multiple EBSCO KBs" scenario"

      Requirements

      • KB credentials are retrieved depending on the current user
      • ConfigurationService works only with user relevant KB configuration

      Acceptance Criteria

      • HoldingsIQ services operate with user related KB only
      • changes covered with unit tests

      TestRail: Results

        Attachments

          Issue Links

            defines

            New Feature - New feature requests UXPROD-1994 eholdings app | Single Tenant w/ Multiple Libraries Support

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            has to be done before

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODKBEKBJ-425 Support holdingsIQ client library to work with mod-kb-ebsco-java

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODKBEKBJ-433 Update RMAPITemplate to use new configuration routine

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODKBEKBJ-390 Spike: describe design for "Single tenant multiple EBSCO KBs" scenario

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            relates to

            Task - A task that needs to be done. MODKBEKBJ-398 Spike "Single tenant + KBs": Updating existing endpoints for providers/packages/resources/titles

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Activity

              People

                dmtkachenko Dmytro Tkachenko
                dmtkachenko Dmytro Tkachenko
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases