Thank you Fabio
Today I got around to implement it, and this method of activation works.
However, I still think that the clients should not be concerned with
exactly what resources someone is propagated to. It is the responsibility
of the IDM system to handle this, not of the client calling the
Il 28/05/2013 11:17, Jesse van Bekkum ha scritto:
Hi
I looked in to it yesterday evening, and this is an example on how to
reproduce this issue on a blank syncope installation.
I did two things to the code. I added this class:
public class Propagate extends AbstractActivitiDelegate {
Could you have a look at this issue, or at least tell me what Log files to
look at?
Using the method you described I just cannot provision (or deprovision)
already existing users, and this is a serious issue for my project (and for
syncope in general, what's an IDM product that cannot provision
Hi Francesco
I have used the code above to provision a resource. On a user that has not
been created yet (id = null) it works fine. However, on another user who
already existed, it does not provision. When I do another update action on
that user, even on a completely unrelated attribute, it
