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.
> 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?
yep
>
> 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?
update will be triggered
> 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 ?
At the moment it cannot be configured. Probably this feature could be stuff for
roadmap.
> Suppose I have 2 sources with 'Sync' capability enabled, how can we ensure
> that circular sync/calls are avoided ?
Ummm, you must avoid to check create/update/delete capabilities on the
resources under synchronization.
If you cannot do this probably you cannot avoid circular sync/calls.
> What is the REST API for explicitly invoking a 'Sync' task?
The path is the following
/syncope/rest/task/execute/{taskId}
The method is TaskController execute method
@PreAuthorize("hasRole('TASK_EXECUTE')")
@RequestMapping(method = RequestMethod.POST, value = "/execute/{taskId}")
public TaskExecTO execute(@PathVariable("taskId") final Long taskId,
@RequestParam(value = "dryRun", defaultValue = "false") final
boolean dryRun) throws NotFoundException {
....
}
Regards,
F.
