Uploaded image for project: 'RAML Module Builder'
  1. RAML Module Builder
  2. RMB-353

Metadata without user id

    XMLWordPrintable

Details

    • Core: Platform - Sprint 60, Core: Platform - Sprint 61, CP: sprint 63, CP: sprint 64
    • 3
    • Core: Platform

    Description

      When a record is updated in anonymous request (no information about user id in request for example after an login attempt has failed) metadata is not populated.
      This causes error in the trigger if record has been previously saved with metadata.

      Two proposals were discussed in the platform-core meeting:
      a) Use some pre-defined default or system user id (RMB-320). This has been rejected.
      b) Handle a missing user id gracefully. This has been decided to be implemented.

      This is to be done for b)

      • Change the trigger so that it handles this case gracefully.
      • Document how the trigger works in the documentation (README, RAML).
      • Make sure that the timestamp is provided by the client that calls the SQL with the trigger and is not provided by the database server.

      TestRail: Results

        Attachments

          1. mod-inventory-storage.txt
            1.77 MB
          2. mod-users.txt
            160 kB
          3. out.txt
            377 kB

          Issue Links

            blocks

            Task - A task that needs to be done. UIU-941 Handle missing createdByUserId and updatedByUserId gracefully

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODUSERS-101 SPIKE - Determine the approach for updating user record in an anonymous request

            • 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. UIU-590 Frontend: Security: Handling Failed login attempts via Folio Login Screen - Lock Account

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

            New Feature - New feature requests RMB-373 Enable/disable logging date and user per tenant and table

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

            New Feature - New feature requests RMB-423 RestVerticle validates X-Okapi-User-Id

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

            Task - A task that needs to be done. FOLIO-1781 Change metadata when user performing action is unknown

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

            Bug - A problem which impairs or prevents the functions of the product. RMB-320 Updating records containing metadata causes exceptions in database trigger

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

            Bug - A problem which impairs or prevents the functions of the product. RMB-366 Anonymizing/Scrubbing Metadata (createdDate, createdByUserId)

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

            Activity

              People

                julianladisch Julian Ladisch
                julianladisch Julian Ladisch
                Adam Dickmeiss Adam Dickmeiss
                Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases