Thanks Fabio! Regards, Antony.
On Thu, Apr 19, 2012 at 1:24 PM, Fabio Martelli <[email protected]>wrote: > Hi All, > starting from Antony's considerations I added something the the roadmap > .... > > 1. possibility to execute propagations in parallel > 2. avoid useless propagations (should solve "circular sync/calls" problem) > > Regards, > F. > > Il giorno 18/apr/2012, alle ore 11.20, Antony Pulicken ha scritto: > > Hi, > > I would like to get some clarifications on some of the fundamental > concepts in Syncope. Please find the questions below and appreciate if you > can answer them all. > > 1. I'm trying to update an attribute of the user (let's say phone > number) in syncope. We have two target systems configured for these > resources (AD and LDAP). I don't have a mapping for 'phone number' in LDAP > resource. Will an update be triggered to LDAP in this case? > 2. If I update the phone number in Syncope, with the same value as in > AD, will the update get triggered to AD ? or it retrieves the value first > form AD and will do the update only if the value is different? > 3. Suppose we have configured Syncope to provision the user to 10 > target systems, will the actual provision happen sequentially? Is there a > way we can configure it to execute paralally (multi threading?) so that we > can still keep it synchronous with a faster response time ? > 4. Suppose I have 2 sources with 'Sync' capability enabled, how can we > ensure that circular sync/calls are avoided ? > 5. What is the REST API for explicitly invoking a 'Sync' task? > > Thanks and Regards, > Antony. > > >
