Uploaded image for project: 'ui-inn-reach'
  1. ui-inn-reach
  2. UIINREACH-15

INN-Reach General Settings: Central Server Connection Configuration Add Central Server Key/Secret Entry Form

    XMLWordPrintable

    Details

    • Template:
      Front-end User Story Template
    • Story Points:
      5
    • Development Team:
      Volaris

      Description

      Purpose:

      In order to integrate with an INN-Reach central server, FOLIO must store a the configurations necessary to connect to and communicate with the central server. This includes the name of the server, an optional description, the agency codes hosted by the FOLIO server (mapped to FOLIO library records), the FOLIO loan type to associate with items borrowed from other local servers in the consortium, the Central server base URL, the API key and secret for authenticating to the central server, and the API key and secret for the central server to use when communicating with FOLIO.

      User story statement(s):

      As a FOLIO administrator with permission to edit INN-Reach central server configurations, I want create, update, or delete a central server configuration INN-Reach settings, so that my FOLIO tenant can participate in the indicated INN-Reach consortium.

      Scenarios:

      1. Scenario:
        • Given the interface scenarios described in UIINREACH-12
        • When creating or editing a central server configuration
        • Then there should be an accordion with form fields to to manage:
          • Central server base URL (required)
          • Central Server API Key/Secret Pair (required)
          • Local Server API Key/Secret Pair
      2. Scenario
        • Given the previous scenario and those in UIINREACH-14
        • When the user attempts to save the create/edit form
        • Then, in addition to the actions described in UIINREACH-14, we will also attempt to validate the Central Server API key/secret pair by trying to retrieve a valid bearer token via the D2IR API token endpoint (D2IR API Documentation, pg. 8)
      3. Scenario
        • Given the key validation attempt
        • When the central server returns a valid auth token
        • Then the key/secret (MODINREACH-9) and base url configuration are saved along with the rest of the form
      4. Scenario
        • Given the key validation attempt
        • When the server returns an authentication error
        • Then the form submission does not occur and the user is returned to the in-progress form with validation errors indicated for the key/secret pair
      5. Scenario
        • Given the key validation attempt
        • When the server returns a connection error
        • Then the form submission does not occur and the user is returned to the in-progress form with validation errors indicated for the base central server base URL

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                brookstravis Brooks Travis
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases