Uploaded image for project: 'FOLIO'
  1. FOLIO
  2. FOLIO-2551

SPIKE: System and Tenant Level Users - Requirements

    XMLWordPrintable

Details

    • Task
    • Status: Closed (View Workflow)
    • P3
    • Resolution: Done
    • None
    • CP: sprint 117, CP: sprint 118, CP: sprint 119
    • 5
    • Core: Platform

    Description

      Overview

      The topic of system and tenant level users has come up a few times in various contexts. This investigation is to gather requirements and use cases in a single place.

      • Edge APIs use "institutional users". These are essentially tenant-level users
        • For now provisioning of these users must be done manually, including granting permissions, etc.
        • The login credentials for these institutional users must be stored in a secret store where the edge API can access them.
      • FOLIO-1781 discusses the need/desire for system or tenant-level users in the context of record metadata.
        • If the system creates/modifies a record and there is no user context, what should be used in the record metadata?
          • Loading sample/reference data when enabling a module for a tenant
          • mod-pub-sub
          • TBD
      • Most recently, there were discussions about system user used by certain modules, for example mod-search and mod-pubsub. See discussion of this PR

      Link to the description of the possible approaches: https://wiki.folio.org/display/~mikhail.fokanov/Module+users+in+Folio

      TestRail: Results

        Attachments

          Issue Links

            relates to

            Task - A task that needs to be done. FOLIO-1786 SPIKE: evaluate "init" tokens as a way to trigger system tasks

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

            New Feature - New feature requests FOLIO-1935 Service creating ROLE and SCHEMA on tenant initialization

            • P2 - normal priority level, must be included in the current development cycle
            • Draft

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. RMB-743 Add preserveMetadata query parameter to insert/update web APIs to allow client to set metadata info while logged in as admin

            • P2 - normal priority level, must be included in the current development cycle
            • Draft

            New Feature - New feature requests RMB-747 Spike: Allow users to authenticate with a 3rd party app which performs actions in FOLIO on their behalf

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. EDGINREACH-2 Provide "Third Party" OAuth2 Token Endpoint for Central Server Authentication to FOLIO

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            New Feature - New feature requests MODINREACH-72 Prepare institutional user for the EDGE module to provide access to application gateway

            • P2 - normal priority level, must be included in the current development cycle
            • Draft

            Bug - A problem which impairs or prevents the functions of the product. MODOAIPMH-243 update edge module institutional user permissions

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

            Page Loading...

            Activity

              People

                mikhail.fokanov Mikhail Fokanov
                cmcnally Craig McNally
                Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases