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

ICF Provisioner Service needs to support system objects with path expression as ID

    Details

    • Verified Version/s:
    • Sprint:
      OpenIDM Sprint 43, OpenIDM Sprint 44
    • Cases:
    • Support Ticket IDs:

      Description

      Copied from bug OPENICF-429:

      On openidm 3.1, recon on google connector will fail managed orgunit -> google SUB orgunit citing "resource name not found" . Sub orgunit name is used as id e.g. "/orgA/subOrgAA". I'm able to reproduce with simple GET /openidm/system/google/OrgUnit/subOrgA/SubOrgAA and error would be:

      { "code": 404, "reason": "Not Found", "message": "Resource 'subOrgA/SubOrgAA' not found" }

      This works fine if not using sub org e.g. GET /openidm/system/google/OrgUnit/subOrgA

      This appears to be due to the fact that the CREST request handler does not handle the sub orgunit ID which is represented as a path expression in the form "/myorg/subA/subB" (See OPENICF-429 comments).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                cgdrake Chris Drake
                Reporter:
                mark.offutt Mark Offutt [X] (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: