[midPoint] approve provisioning from LiveSync

[Pavol Mederly]

Hello Ramiji,


the feature you're trying to use, i.e. approving changes that were 
detected by LiveSync, has not been implemented yet.


We first implemented the most common scenario: approving explicitly 
requested changes (submitted via GUI, Java, SOAP or REST API).


What you need is probably not that hard to implement. What needs to be 
clarified is exact expected behavior - for example, should we consider 
changes detected only by LiveSync, or by reconciliation as well?

     a) If by LiveSync only: what with changes that would get lost 
(somehow - it might happen for reasons internal or external to 
midPoint). Normally, such changes are covered by reconciliation. If we 
would forbid reconciliation, we would have to have another mechanism for 
recovering such forgotten/lost changes.

     b) If by reconciliation as well: what with changes that would be 
rejected? They would trigger new approval process at each reconciliation 
task run.


Best regards,

Pavol


On 05.05.2016 15:07, Rijndaal Ramiji wrote:
>
> Hi.
>
> I'm currently studying workflows, and my admin project would like to 
> use it in the LiveSync provisioning process.
>
> We currently have an HR resource that has a livesync task.
> An object template for the sync event of HR can create the CN for AD 
> and stores it in $user/extension/CN.
>
> Finally, My ActiveDirectory resource has on outbound mapping  of 
> $user/extension/CN in icfs:name.
>
> It works like a charm! (this product is quite of amazing ;) )
>
>
> Btw,  I'm reading about workflows of approval and we would like to 
> make the liveSync process of provisioning to be overlooked by a workflow.
>
> I have configured the workflow process, and it works for, example, 
> creation of an user from MidPoint "new user".
>
> Before the effective provisioning on AD, it ask to the admin to reject 
> or approve the request of creation.
>
> This workflow sadly, seems to not work with the automatic creation of 
> the account from the "unmatched" reaction...
>
> Is this a known bug , should this be the exact flow or maybe I have 
> made something wrong?
>
> Thank you all!
>
>
>
> _______________________________________________
> 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/20160505/95701598/attachment.htm>