[midPoint] Multiple IDs (correlation) on resource

[Davy Priem]

Hi Jason,

On the roadmap I see they will introduce ‘Personas: (identity links): Ability to link user objects representing physical person and his personas, e.g. employee persona, administration persona, etc.’. Isn’t this what you’re looking for?

Best regards,
Davy Priem

Van: midPoint [mailto:midpoint-bounces at lists.evolveum.com] Namens Jason Everling
Verzonden: dinsdag 7 februari 2017 1:49
Aan: midPoint General Discussion <midpoint at lists.evolveum.com>
Onderwerp: [midPoint] Multiple IDs (correlation) on resource

I am working on adding a resource in which each type of person can have a different ID, (uuid) , such as faculty/staff/contractors/etc.. would match using their username (name) and students/alumni/guests would match using their campus id.

I couldn't find too much on this or samples, does anybody have anything similar?

This kind of resource is new to me but reading up on the wiki I am leaning towards multiple (intents)??? Would that be down the right road? For example

<objectType>
<displayName>Student Account</displayName>
<intent>studentAccount</intent>
<default>true</default>
....
...
</objectType>
<objectType>
<displayName>Staff Account</displayName>
<intent>staffAccount</intent>
<default>true</default>
....
...
</objectType>

<synchronization>
<objectSynchronization>
            <enabled>true</enabled>
            <intent>studentAccount</intent>
                        <correlation>
                                    <q:equal>
                                               <q:path>c:extension/bshp:campusID</q:path>
........
.......
     </objectSynchronization>
    <objectSynchronization>
            <enabled>true</enabled>
            <intent>staffAccount</intent>
                        <correlation>
                                    <q:equal>
                                               <q:path>c:name</q:path>
........
.......
     </objectSynchronization>
</synchronization>

Any help is always appreciated!

JASON

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20170210/c07e7768/attachment.htm>