Uploaded image for project: 'MidPoint'
  1. MidPoint
  2. MID-7966

Sudden appearance of error 'Composite secondary identifier is not supported yet'

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 4.4.1
    • Fix Version/s: 4.6
    • Component/s: Connectors
    • Labels:
      None
    • Environment:

      running Internet2's midPoint container in AWS-ECS with a "native" postgres DB

    • Subscription:
      Active subscription

      Description

      Users are imported from a SQL resource and an account is created in a downstream LDAP resource.  That all works fine, but some time later, with no detectable change in the underlying data, midPoint will start throwing the error 'Composite secondary identifier is not supported yet' for some relatively small subset of our users (currently 238 users out of 6000).  I can fix this on a per-user basis by deleting the related LDAP resource shadow in the repository as well as the actual LDAP account then recomputing the user in midPoint.  Then, midPoint will re-provision the LDAP account in a way that it is then happy with (also with no change in the underlying data).

        Attachments

          Activity

            People

            Assignee:
            mederly Pavol Mederly
            Reporter:
            pcaskey Paul Caskey
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: