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 <[email protected]>
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/
