[midPoint] Running a recomputation on a subset of users

[Pavol Mederly]

Hello Tom,

yes, it's perfectly possible. Just use objectQuery extension attribute:

<task
xmlns="http://midpoint.evolveum.com/xml/ns/public/common/common-3"
xmlns:mext="http://midpoint.evolveum.com/xml/ns/public/model/extension-3"
xmlns:q="http://prism.evolveum.com/xml/ns/public/query-3">

     <name>User Recompute (users in Bratislava)</name>
     <extension>
         <mext:objectQuery>
             <q:filter>
                 <q:equal>
<q:path>locality</q:path>
<q:value>Bratislava</q:value>
                 </q:equal>
             </q:filter>
         </mext:objectQuery>
     </extension>

     <ownerRef oid="00000000-0000-0000-0000-000000000002"/>
<executionStatus>runnable</executionStatus>
<handlerUri>http://midpoint.evolveum.com/xml/ns/public/model/synchronization/task/recompute/handler-3</handlerUri>
     <recurrence>single</recurrence>
     <binding>tight</binding>
</task>

Best regards,
Pavol

On 18. 3. 2015 12:19, Tom Gerrard wrote:
>
> Hi all,
>
> I was just wondering if there is any way of running the User 
> Recomputation task on a subset of users?
>
> I am trying to populate an attribute on the user object with the DN of 
> the matching account in an assigned resource.  I’ve updated the 
> assigned resource definition so that it has an inbound mapping for 
> icfs:name pointing at an extension attribute.
>
> If I run a user recomputation (or check reconcile and save on the 
> user’s page in the web interface) then it is updated correctly.  
> Unfortunately as some accounts associated to the users in this 
> instance are unavailable or very slow, processing all users could take 
> a very long time (based on the average speed so far about 19 days!).  
> If it were possible to limit the recomputation to users with a 
> specific locality attribute we could only process users where the 
> resources for all their accounts are available.
>
> I did wonder if a reconciliation on either the ‘source’ resource or 
> the assigned resource would update the attribute but it doesn’t seem 
> to do it in this case.
>
> Thanks,
>
> Tom
>
>
>
> _______________________________________________
> 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/20150318/5aede459/attachment.htm>