You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by Colm O hEigeartaigh <co...@apache.org> on 2014/06/24 12:24:46 UTC
Task "Rules"
Hi all,
What are the new task "rules" that have been added to trunk? When I create
a new synchronization task with the default "Matching/Update"
"Unmatching/Assign", it appears that the selected LDAPPasswordSyncActions
class is not run.
Colm.
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: Task "Rules"
Posted by andrea patricelli <an...@tirasa.net>.
Il 24/06/2014 12:24, Colm O hEigeartaigh ha scritto:
> Hi all,
Hi Colm,
> What are the new task "rules" that have been added to trunk? When I create
> a new synchronization task with the default "Matching/Update"
> "Unmatching/Assign", it appears that the selected LDAPPasswordSyncActions
> class is not run.
I created a new sync task with LDAPPasswordSyncActions class assigned
and default Matching/Unmatching rules, very similar to LDAP Sync Task.
Then I ran this test task and, debugging, I noticed that after() method
of LDAPPasswordSyncActions class is ever executed (create, update);
beforeCreate() method instead, when creating new user/role instance on
Syncope, is never used due to the fact that SyncopeSyncResultHandler
never calls:
protected List<SyncResult> create(final SyncDelta delta, final
AttributableUtil attrUtil, final boolean dryRun).
that calls beforeCreate() for each sync action available.
So I think that class LDAPPasswordSyncActions is run, and there's
another problem.
But maybe I'm missing something, I'll investigate deeper today.
> Colm.
>
>
Best Regards,
Andrea
--
Dott. Andrea Patricelli
Tel +393204524292
Junior Engineer @ Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +390859116307 / FAX +39 0859111173
http://www.tirasa.net
Re: Task "Rules"
Posted by Colm O hEigeartaigh <co...@apache.org>.
Cool, thanks! It's working fine now.
Colm.
On Wed, Jun 25, 2014 at 10:06 AM, andrea patricelli <
andrea.patricelli@tirasa.net> wrote:
> Il 25/06/2014 08:28, Francesco Chicchiriccò ha scritto:
>
> Hi,
>> it seems that this problem - probably related to SYNCOPE-473 - is
>> blocking the finalization of SYNCOPE-505: Fabio, Andrea, who is going to
>> take a look at what is happening?
>>
>>
> Hi Colm,
>
> I worked on this issue.
> You and Francesco were right, the problem was in Sync Task Unmatching rule
> default value set in console SyncTaskModalPage. In order to make
> LDAPPasswordSyncActions working fine as you expected, sync task needs to
> have Unmatching rule set to PROVISION (and not to ASSIGN that is Push Task
> default Unmatching rule value).
>
>
> Side note: we absolutely need to document this amazing new feature (Push
>> and matching / unmatching rules).
>>
>> Regards.
>>
>> On 24/06/2014 13:18, Colm O hEigeartaigh wrote:
>>
>>> Ok, thanks for the explanation! I suspect it is a UI bug caused by the
>>> merge for SYNCOPE-473, as it was definately working for me last week:
>>>
>>> https://issues.apache.org/jira/browse/SYNCOPE-473
>>>
>>> Colm.
>>>
>>>
>>> On Tue, Jun 24, 2014 at 11:50 AM, Fabio Martelli <
>>> fabio.martelli@gmail.com>
>>> wrote:
>>>
>>> Il 24/06/2014 12:24, Colm O hEigeartaigh ha scritto:
>>>>
>>>> Hi all,
>>>>
>>>>> What are the new task "rules" that have been added to trunk? When I
>>>>> create
>>>>> a new synchronization task with the default "Matching/Update"
>>>>> "Unmatching/Assign", it appears that the selected
>>>>> LDAPPasswordSyncActions
>>>>> class is not run.
>>>>>
>>>>> Colm.
>>>>>
>>>>>
>>>>> Hi Colm, matching/unmatching rules can be configured in order to
>>>>> specify
>>>>>
>>>> a specific behaviour in case of matching (sync user found locally) and
>>>> unmatching (sync user not found locally) scenarios.
>>>>
>>>> For example, I can ask to syncope to unlink the synchronized resource
>>>> from
>>>> the local account that matches the synchronized one.
>>>>
>>>> This is the issue [1], still in progress: maybe you are facing with a
>>>> bug
>>>> (maybe just on the admin console).
>>>> If you can/want, please investigate more, otherwise, be patient: we will
>>>> fix it very soon.
>>>>
>>>> Best regards,
>>>> F.
>>>>
>>>> [1] https://issues.apache.org/jira/browse/SYNCOPE-471
>>>>
>>>
>> Best regards,
> Andrea
>
> --
> Dott. Andrea Patricelli
> Tel +393204524292
>
> Junior Engineer @ Tirasa S.r.l.
> Viale D'Annunzio 267 - 65127 Pescara
> Tel +390859116307 / FAX +39 0859111173
> http://www.tirasa.net
>
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: Task "Rules"
Posted by Fabio Martelli <fa...@gmail.com>.
Il 25/06/2014 11:06, andrea patricelli ha scritto:
> Il 25/06/2014 08:28, Francesco Chicchiriccò ha scritto:
>> Hi,
>> it seems that this problem - probably related to SYNCOPE-473 - is
>> blocking the finalization of SYNCOPE-505: Fabio, Andrea, who is going
>> to take a look at what is happening?
>>
>
> Hi Colm,
>
> I worked on this issue.
> You and Francesco were right, the problem was in Sync Task Unmatching
> rule default value set in console SyncTaskModalPage. In order to make
> LDAPPasswordSyncActions working fine as you expected, sync task needs
> to have Unmatching rule set to PROVISION (and not to ASSIGN that is
> Push Task default Unmatching rule value).
Hi All, please note that action's before method set has been changed a lot.
Currently, available options are:
* beforeCreate
executed before local user/group create in case of unmatching solved
with PROVISION rule (default rule)
* beforeAssign
executed before assigning (create + link) the synchronized resource to a
local user/group in case of unmatching solved with ASSIGN rule
* beforeUnassign
executed before unassigning (unlink + deprovision) the synchronized
resource from a local user/group in case of matching solved with
UNASSIGN rule
* beforeDeprovision
executed before deprovisioning (deprovision without unlink) the matching
user/group from the synchronized resource in case of matching solved
with DEPROVISION rule
* beforeUnlink
executed before unlinking (unlink without deprovision or update)
thematching user/group from the synchronized resource in case of
matching solved with UNLINK rule
* beforeLink
executed before linking (link without update) thematching user/group
from the synchronized resource in case of matching solved with LINK rule
* beforeUpdate
executed before updating the matching user/group in case of matching
solved with UPDATE rule (default rule)
* beforeDelete
executed before deleting a local user/group matching the synchronized
removed identity
Best regards,
F.
>
>> Side note: we absolutely need to document this amazing new feature
>> (Push and matching / unmatching rules).
>>
>> Regards.
>>
>> On 24/06/2014 13:18, Colm O hEigeartaigh wrote:
>>> Ok, thanks for the explanation! I suspect it is a UI bug caused by the
>>> merge for SYNCOPE-473, as it was definately working for me last week:
>>>
>>> https://issues.apache.org/jira/browse/SYNCOPE-473
>>>
>>> Colm.
>>>
>>>
>>> On Tue, Jun 24, 2014 at 11:50 AM, Fabio Martelli
>>> <fa...@gmail.com>
>>> wrote:
>>>
>>>> Il 24/06/2014 12:24, Colm O hEigeartaigh ha scritto:
>>>>
>>>> Hi all,
>>>>> What are the new task "rules" that have been added to trunk? When
>>>>> I create
>>>>> a new synchronization task with the default "Matching/Update"
>>>>> "Unmatching/Assign", it appears that the selected
>>>>> LDAPPasswordSyncActions
>>>>> class is not run.
>>>>>
>>>>> Colm.
>>>>>
>>>>>
>>>>> Hi Colm, matching/unmatching rules can be configured in order to
>>>>> specify
>>>> a specific behaviour in case of matching (sync user found locally) and
>>>> unmatching (sync user not found locally) scenarios.
>>>>
>>>> For example, I can ask to syncope to unlink the synchronized
>>>> resource from
>>>> the local account that matches the synchronized one.
>>>>
>>>> This is the issue [1], still in progress: maybe you are facing with
>>>> a bug
>>>> (maybe just on the admin console).
>>>> If you can/want, please investigate more, otherwise, be patient: we
>>>> will
>>>> fix it very soon.
>>>>
>>>> Best regards,
>>>> F.
>>>>
>>>> [1] https://issues.apache.org/jira/browse/SYNCOPE-471
>>
> Best regards,
> Andrea
>
--
Fabio Martelli
Tirasa - Open Source Excellence
http://www.tirasa.net/
Apache Syncope PMC
http://people.apache.org/~fmartelli/
Re: Task "Rules"
Posted by andrea patricelli <an...@tirasa.net>.
Il 25/06/2014 08:28, Francesco Chicchiriccò ha scritto:
> Hi,
> it seems that this problem - probably related to SYNCOPE-473 - is
> blocking the finalization of SYNCOPE-505: Fabio, Andrea, who is going
> to take a look at what is happening?
>
Hi Colm,
I worked on this issue.
You and Francesco were right, the problem was in Sync Task Unmatching
rule default value set in console SyncTaskModalPage. In order to make
LDAPPasswordSyncActions working fine as you expected, sync task needs to
have Unmatching rule set to PROVISION (and not to ASSIGN that is Push
Task default Unmatching rule value).
> Side note: we absolutely need to document this amazing new feature
> (Push and matching / unmatching rules).
>
> Regards.
>
> On 24/06/2014 13:18, Colm O hEigeartaigh wrote:
>> Ok, thanks for the explanation! I suspect it is a UI bug caused by the
>> merge for SYNCOPE-473, as it was definately working for me last week:
>>
>> https://issues.apache.org/jira/browse/SYNCOPE-473
>>
>> Colm.
>>
>>
>> On Tue, Jun 24, 2014 at 11:50 AM, Fabio Martelli
>> <fa...@gmail.com>
>> wrote:
>>
>>> Il 24/06/2014 12:24, Colm O hEigeartaigh ha scritto:
>>>
>>> Hi all,
>>>> What are the new task "rules" that have been added to trunk? When I
>>>> create
>>>> a new synchronization task with the default "Matching/Update"
>>>> "Unmatching/Assign", it appears that the selected
>>>> LDAPPasswordSyncActions
>>>> class is not run.
>>>>
>>>> Colm.
>>>>
>>>>
>>>> Hi Colm, matching/unmatching rules can be configured in order to
>>>> specify
>>> a specific behaviour in case of matching (sync user found locally) and
>>> unmatching (sync user not found locally) scenarios.
>>>
>>> For example, I can ask to syncope to unlink the synchronized
>>> resource from
>>> the local account that matches the synchronized one.
>>>
>>> This is the issue [1], still in progress: maybe you are facing with
>>> a bug
>>> (maybe just on the admin console).
>>> If you can/want, please investigate more, otherwise, be patient: we
>>> will
>>> fix it very soon.
>>>
>>> Best regards,
>>> F.
>>>
>>> [1] https://issues.apache.org/jira/browse/SYNCOPE-471
>
Best regards,
Andrea
--
Dott. Andrea Patricelli
Tel +393204524292
Junior Engineer @ Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +390859116307 / FAX +39 0859111173
http://www.tirasa.net
Re: Task "Rules"
Posted by Francesco Chicchiriccò <il...@apache.org>.
Hi,
it seems that this problem - probably related to SYNCOPE-473 - is
blocking the finalization of SYNCOPE-505: Fabio, Andrea, who is going to
take a look at what is happening?
Side note: we absolutely need to document this amazing new feature (Push
and matching / unmatching rules).
Regards.
On 24/06/2014 13:18, Colm O hEigeartaigh wrote:
> Ok, thanks for the explanation! I suspect it is a UI bug caused by the
> merge for SYNCOPE-473, as it was definately working for me last week:
>
> https://issues.apache.org/jira/browse/SYNCOPE-473
>
> Colm.
>
>
> On Tue, Jun 24, 2014 at 11:50 AM, Fabio Martelli <fa...@gmail.com>
> wrote:
>
>> Il 24/06/2014 12:24, Colm O hEigeartaigh ha scritto:
>>
>> Hi all,
>>> What are the new task "rules" that have been added to trunk? When I create
>>> a new synchronization task with the default "Matching/Update"
>>> "Unmatching/Assign", it appears that the selected LDAPPasswordSyncActions
>>> class is not run.
>>>
>>> Colm.
>>>
>>>
>>> Hi Colm, matching/unmatching rules can be configured in order to specify
>> a specific behaviour in case of matching (sync user found locally) and
>> unmatching (sync user not found locally) scenarios.
>>
>> For example, I can ask to syncope to unlink the synchronized resource from
>> the local account that matches the synchronized one.
>>
>> This is the issue [1], still in progress: maybe you are facing with a bug
>> (maybe just on the admin console).
>> If you can/want, please investigate more, otherwise, be patient: we will
>> fix it very soon.
>>
>> Best regards,
>> F.
>>
>> [1] https://issues.apache.org/jira/browse/SYNCOPE-471
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC
http://people.apache.org/~ilgrosso/
Re: Task "Rules"
Posted by Colm O hEigeartaigh <co...@apache.org>.
Ok, thanks for the explanation! I suspect it is a UI bug caused by the
merge for SYNCOPE-473, as it was definately working for me last week:
https://issues.apache.org/jira/browse/SYNCOPE-473
Colm.
On Tue, Jun 24, 2014 at 11:50 AM, Fabio Martelli <fa...@gmail.com>
wrote:
> Il 24/06/2014 12:24, Colm O hEigeartaigh ha scritto:
>
> Hi all,
>>
>> What are the new task "rules" that have been added to trunk? When I create
>> a new synchronization task with the default "Matching/Update"
>> "Unmatching/Assign", it appears that the selected LDAPPasswordSyncActions
>> class is not run.
>>
>> Colm.
>>
>>
>> Hi Colm, matching/unmatching rules can be configured in order to specify
> a specific behaviour in case of matching (sync user found locally) and
> unmatching (sync user not found locally) scenarios.
>
> For example, I can ask to syncope to unlink the synchronized resource from
> the local account that matches the synchronized one.
>
> This is the issue [1], still in progress: maybe you are facing with a bug
> (maybe just on the admin console).
> If you can/want, please investigate more, otherwise, be patient: we will
> fix it very soon.
>
> Best regards,
> F.
>
> [1] https://issues.apache.org/jira/browse/SYNCOPE-471
>
> --
> Fabio Martelli
>
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
>
> Apache Syncope PMC
> http://people.apache.org/~fmartelli/
>
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: Task "Rules"
Posted by Fabio Martelli <fa...@gmail.com>.
Il 24/06/2014 12:24, Colm O hEigeartaigh ha scritto:
> Hi all,
>
> What are the new task "rules" that have been added to trunk? When I create
> a new synchronization task with the default "Matching/Update"
> "Unmatching/Assign", it appears that the selected LDAPPasswordSyncActions
> class is not run.
>
> Colm.
>
>
Hi Colm, matching/unmatching rules can be configured in order to specify
a specific behaviour in case of matching (sync user found locally) and
unmatching (sync user not found locally) scenarios.
For example, I can ask to syncope to unlink the synchronized resource
from the local account that matches the synchronized one.
This is the issue [1], still in progress: maybe you are facing with a
bug (maybe just on the admin console).
If you can/want, please investigate more, otherwise, be patient: we will
fix it very soon.
Best regards,
F.
[1] https://issues.apache.org/jira/browse/SYNCOPE-471
--
Fabio Martelli
Tirasa - Open Source Excellence
http://www.tirasa.net/
Apache Syncope PMC
http://people.apache.org/~fmartelli/