Uploaded image for project: 'OpenIDM'
  1. OpenIDM
  2. OPENIDM-4078

'400 Bad Request error' can occur when try to display Mapping page in UI with audit-sample

    Details

    • Cases:
    • Support Ticket IDs:

      Description

      Sometimes, if you are use an external jdbc repository for audit logs, when you try to display the Mapping page in the UI, the display will fail with '400 Bad Request error'. The problem seems to be that if the name of the resource that you're trying to display is not yet in memory, line 170 of openidm.sync.impl.ReconciliationService.java will incorrectly try to use a queryId. With the patch for OPENIDM-2834, the audit service should use queryFilters and not queryId's.

      Steps to Reproduce:

      1. Install openidm 3.1 with the patch for OPENIDM-3873.
      2. Start openidm with the audit-sample project.
      3. Select the 'Mappings' tab

      Expected Results: Mappings page should display

      Actual Results: "Bad Request error" flashes across the top of the Resources page and the Mapping page doesn't display.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                andi andi
                Reporter:
                nena.hunt Nena Hunt
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: