Return-Path: X-Original-To: apmail-incubator-syncope-user-archive@minotaur.apache.org Delivered-To: apmail-incubator-syncope-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C7C6995C3 for ; Thu, 19 Apr 2012 08:53:32 +0000 (UTC) Received: (qmail 88151 invoked by uid 500); 19 Apr 2012 08:53:32 -0000 Delivered-To: apmail-incubator-syncope-user-archive@incubator.apache.org Received: (qmail 88089 invoked by uid 500); 19 Apr 2012 08:53:32 -0000 Mailing-List: contact syncope-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: syncope-user@incubator.apache.org Delivered-To: mailing list syncope-user@incubator.apache.org Received: (qmail 88072 invoked by uid 99); 19 Apr 2012 08:53:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Apr 2012 08:53:31 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of antony.pulicken@gmail.com designates 74.125.82.175 as permitted sender) Received: from [74.125.82.175] (HELO mail-we0-f175.google.com) (74.125.82.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Apr 2012 08:53:23 +0000 Received: by wera1 with SMTP id a1so5323034wer.6 for ; Thu, 19 Apr 2012 01:53:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=t0Aqa2h8mFsY9ILp19S7TB1+wm7+laZhHL1r2qWOLek=; b=KTUm3roC/rKKqz+MGBg+Q2XUlHxr7SoVrwrtproD/EQqptrpElYqs7bxSqIfJ0tFiy K3wIoZ84YWt2sqtE023BdEnacuYaNzLF1fQokTBPX+P73V3Mssw54gaZPTHm9FgXxdqR mneqAs1ggE50dmPR12LSxLc5GCe4NJZnXSqvTUGlxrID21AKWlaZTUlokOi0tueMV+QO vcmV6NQxIf5pymYIz1Uz4tAVmrEyNpCVDC4bv98NgCC1AlQHYcLYgEDmTxmM5nl9OgPR U4nMcoCfV1mhXgYXJMsutjkkjCcuxbTms6Cbz088s3SdR15OFLJC+Jtqh3ls/ta8Cj7Q f/bw== MIME-Version: 1.0 Received: by 10.216.136.13 with SMTP id v13mr800167wei.32.1334825583366; Thu, 19 Apr 2012 01:53:03 -0700 (PDT) Received: by 10.223.127.216 with HTTP; Thu, 19 Apr 2012 01:53:03 -0700 (PDT) In-Reply-To: References: Date: Thu, 19 Apr 2012 14:23:03 +0530 Message-ID: Subject: Re: Need few clarifications From: Antony Pulicken To: syncope-user@incubator.apache.org Content-Type: multipart/alternative; boundary=0016e6dd98e2bbd1f404be044c62 --0016e6dd98e2bbd1f404be044c62 Content-Type: text/plain; charset=ISO-8859-1 Thanks Fabio! Regards, Antony. On Thu, Apr 19, 2012 at 1:24 PM, Fabio Martelli 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. > > > --0016e6dd98e2bbd1f404be044c62 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks Fabio!

Regards,
Antony.

= On Thu, Apr 19, 2012 at 1:24 PM, Fabio Martelli <fabio.martelli@gmail.com> wrote:
Hi All,<= div>starting from Antony's considerations I added something the the roa= dmap ....

1. possibility to execute propagations in parallel
2. avoid useless propagations (should solve "circular sync/calls= "=A0=A0problem)

Regards,
F.

Il giorno 18/apr/2012, alle ore 11.20, Anto= ny Pulicken ha scritto:

Hi,

I would like to get=A0 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 =A0(let's say= phone number) in syncope. We have two target systems configured for these = resources (AD and LDAP).=A0 I don't have a mapping for 'phone numbe= r' in LDAP resource. Will an update be triggered to LDAP in this case?<= br>
  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 =A0provision the user to 10 target sy= stems, 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 ca= n we ensure that circular sync/calls are avoided ?
  5. What is the REST= API for explicitly invoking a 'Sync' task?
Thanks and Reg= ards,
Antony.


--0016e6dd98e2bbd1f404be044c62--