[midPoint] Complex Correlation Rules

Tue Apr 23 16:31:34 CEST 2019

he couldn't use an OR statement because at a given time a person can have 2
records, just like in our case, you can have a faculty/staff member that
are currently enrolled in courses thus are also a student. So there is 2
unique records using different identifiers. Intents solved that for us but
in a larger institution it can become quite complex as noted in the wiki,
https://wiki.evolveum.com/display/midPoint/Synchronization+Sorter

On Tue, Apr 23, 2019 at 9:01 AM Wojciech Staszewski <
wojciech.staszewski at diagnostyka.pl> wrote:

> Hello Martin!
> What about single correlation rule with "OR" and "AND" combination?
>
>
> <q:or xmlns:org="http://midpoint.evolveum.com/xml/ns/public/common/org-3">
>      <q:equal>
>          <q:matching>polyStringNorm</q:matching>
>          <q:path>c:employeeNumber</q:path>
>          <expression>
>              <path>declare namespace ri='
> http://midpoint.evolveum.com/xml/ns/public/resource/instance-3';
>             $account/attributes/ri:employeeNumber</path>
>          </expression>
>      </q:equal>
>      <q:and>
>          <q:equal>
>              <q:matching>polyStringNorm</q:matching>
>              <q:path>c:givenName</q:path>
>              <expression>
>                  <path>declare namespace ri='
> http://midpoint.evolveum.com/xml/ns/public/resource/instance-3';
>                 $account/attributes/ri:firstname</path>
>              </expression>
>          </q:equal>
>          <q:equal>
>              <q:matching>polyStringNorm</q:matching>
>              <q:path>c:familyName</q:path>
>              <expression>
>                  <path>declare namespace ri='
> http://midpoint.evolveum.com/xml/ns/public/resource/instance-3';
>                 $account/attributes/ri:surname</path>
>              </expression>
>          </q:equal>
>      </q:and>
> </q:or>
>
> Cheers!
> WS
>
> W dniu 23.04.2019 o 15:25, Ivan Noris pisze:
> > Hi David,
> >
> > you may need this:
> https://wiki.evolveum.com/display/midPoint/Synchronization+Sorter
> >
> > Best regards,
> >
> > Ivan
> >
> > On 23. 4. 2019 15:15, Martin, David (DIT) wrote:
> >> I'm new to midPoint, just doing a Trial/PoC (v3.9). Currently I have 2
> database resources (one is HR and the other Student Records) configured and
> have successfully imported accounts and generated Users. The Correlation
> rule was a simple match on Employee Number / Student ID (I added a schema
> extension for Student ID).
> >>
> >>
> >> Now I am trying to model a more complex Correlation where it checks
> first based on Employee Number / Student ID and if that isn't found then
> checks based on Given Name and Family Name. The scenario is that a person
> may be both staff and student. The ID Number should be the same in both
> systems but it isn't always picked up, hence the second check.
> >>
> >>
> >> At the moment I have tried to set them up as separate Correlation rules
> within the Synchronization on the Resource, but it seems if the first
> Correlation finds no matches it ignores the second rule . Conversely if the
> first rule finds a match it will also run the second rule. Ultimately I
> want to have multiple rules with different assurance levels. If a high
> assurance rule finds a single match we can stop and linking could occur.
> Other rules would only produce possible matches and require manual review
> and correlation.
> >>
> >>
> >> The system allows multiple Correlation rules, but I couldn't find any
> documentation or examples that explain how to use these. Any thoughts on
> how to approach this or documentation I've missed?
> >>
> >>
> >> thanks
> >>
> >> David
> >>
> >> [Charles Sturt University]<http://www.csu.edu.au/>
> >>
> >> |   ALBURY-WODONGA   |   BATHURST   |   CANBERRA   |   DUBBO   |
>  GOULBURN   |   MELBOURNE   |   ORANGE   |   PORT MACQUARIE   |   SYDNEY
>  |   WAGGA WAGGA   |
> >>
> >> ________________________________
> >> LEGAL NOTICE
> >> This email (and any attachment) is confidential and is intended for the
> use of the addressee(s) only. If you are not the intended recipient of this
> email, you must not copy, distribute, take any action in reliance on it or
> disclose it to anyone. Any confidentiality is not waived or lost by reason
> of mistaken delivery. Email should be checked for viruses and defects
> before opening. Charles Sturt University (CSU) does not accept liability
> for viruses or any consequence which arise as a result of this email
> transmission. Email communications with CSU may be subject to automated
> email filtering, which could result in the delay or deletion of a
> legitimate email before it is read at CSU. The views expressed in this
> email are not necessarily those of CSU.
> >>
> >> Charles Sturt University in Australia<http://www.csu.edu.au>  The
> Grange Chancellery, Panorama Avenue, Bathurst NSW Australia 2795 (ABN: 83
> 878 708 551; CRICOS Provider Number: 00005F (National)). TEQSA Provider
> Number: PV12018
> >>
> >> Consider the environment before printing this email.
> >>
> >>
> >> _______________________________________________
> >> midPoint mailing list
> >> midPoint at lists.evolveum.com
> >> http://lists.evolveum.com/mailman/listinfo/midpoint
> >
> > --
> > Ivan Noris
> > Senior Identity Engineer
> > evolveum.com
> >
> >
> > _______________________________________________
> > midPoint mailing list
> > midPoint at lists.evolveum.com
> > http://lists.evolveum.com/mailman/listinfo/midpoint
> >
>
> --
> Wojciech Staszewski
> Administrator Systemów Sieciowych
> tel. kom: 663 680 236
> www.diagnostyka.pl
> Diagnostyka Sp. z o. o.
> ul. Prof. M. Życzkowskiego 16, 31-864 Kraków
> Numer KRS: 0000381559 (Sąd Rejonowy dla Krakowa-Śródmieścia w Krakowie, XI
> Wydział Gospodarczy KRS)
> NIP: 675-12-65-009; REGON: 356366975
> Kapitał zakładowy: 33 756 500 zł.
>
> Pomyśl o środowisku zanim wydrukujesz ten e-mail.
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20190423/7c21bc94/attachment.htm>