You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@syncope.apache.org by Antony Pulicken <an...@gmail.com> on 2012/04/18 11:20:51 UTC
Need few clarifications
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.
Re: Need few clarifications
Posted by Fabio Martelli <fa...@gmail.com>.
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.
Re: Need few clarifications
Posted by Antony Pulicken <an...@gmail.com>.
Thanks Fabio!
Regards,
Antony.
On Thu, Apr 19, 2012 at 1:24 PM, Fabio Martelli <fa...@gmail.com>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.
>
>
>
Re: Need few clarifications
Posted by Antony Pulicken <an...@gmail.com>.
What I meant was in terms of performance Francesco :-) ! The unnecessary
propagations are costing us a dear in terms of performance and hence I just
wanted to confirm whether all the points that I mentioned will be covered?
Support for parallel execution and asynchronous execution also boost up the
performance.
Regards,
Antony.
On Thu, May 3, 2012 at 12:48 PM, Francesco Chicchiriccò <ilgrosso@apache.org
> wrote:
> On 03/05/2012 09:09, Antony Pulicken wrote:
>
> Thanks Fabio for adding these points to the road map. Hope the 2nd point
> that you added in the road map will take care of the 1st, 2nd and 4th
> points mentioned in my mail. It's really costing us a dear !!
>
>
> Well,
> if you're making money out of it, and if you'd like to get something
> (inside / outside roadmap) done before that the community gets over it, you
> have two options:
> (a) do it yourself
> (b) pay someone: it's the Open Source way of paying bills :-)
>
> Regards.
>
>
> On Thu, Apr 19, 2012 at 1:24 PM, Fabio Martelli <fabio.martelli@gmail.com
> > 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.
>>
>> --
> Francesco Chicchiriccò
>
> Apache Cocoon PMC and Apache Syncope PPMC Memberhttp://people.apache.org/~ilgrosso/
>
>
Re: Need few clarifications
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 03/05/2012 09:09, Antony Pulicken wrote:
> Thanks Fabio for adding these points to the road map. Hope the 2nd
> point that you added in the road map will take care of the 1st, 2nd
> and 4th points mentioned in my mail. It's really costing us a dear !!
Well,
if you're making money out of it, and if you'd like to get something
(inside / outside roadmap) done before that the community gets over it,
you have two options:
(a) do it yourself
(b) pay someone: it's the Open Source way of paying bills :-)
Regards.
> On Thu, Apr 19, 2012 at 1:24 PM, Fabio Martelli
> <fabio.martelli@gmail.com <ma...@gmail.com>> 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.
>
--
Francesco Chicchiriccò
Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
Re: Need few clarifications
Posted by Antony Pulicken <an...@gmail.com>.
Thanks Fabio for adding these points to the road map. Hope the 2nd point
that you added in the road map will take care of the 1st, 2nd and 4th
points mentioned in my mail. It's really costing us a dear !!
Regards,
Antony.
On Thu, Apr 19, 2012 at 1:24 PM, Fabio Martelli <fa...@gmail.com>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.
>
>
>
Re: Need few clarifications
Posted by Fabio Martelli <fa...@gmail.com>.
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.
> 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?
> 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?
> 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 ?
> Suppose I have 2 sources with 'Sync' capability enabled, how can we ensure that circular sync/calls are avoided ?
> What is the REST API for explicitly invoking a 'Sync' task?
> Thanks and Regards,
> Antony.