Great thanks, selecting 'full reconciliation' did the trick. Do you know is there a fix planned to only use the delta with Apache DS?
Another question: After importing user entries from an Apache DS backend, they don't have the corresponding "Resource" selected. So to update a user entry I need to manually select the corresponding Connector before the change gets propagated back. Is this expected? Colm. On Fri, Aug 10, 2012 at 1:25 PM, Francesco Chicchiriccò <[email protected] > wrote: > On 10/08/2012 14.09, Colm O hEigeartaigh wrote: > >> Hi all, >> >> A quick sanity check: Is there any reason why I can't synchronize from an >> Apache DS backend in Syncope? I can create users in Syncope and propagate >> them to the resource fine, but I can't do the reverse. >> > > Hi Colm, > synchronization from an external resource might fail for many different > reasons: I'd suggest to increase the level for the 'org.apache.syncope.core. > **scheduling' logger in order to have some insight about the failure. > > Generally speaking, you can perform a proper synchronization only when the > underlying connector supports the SYNC operation (and has the correspondent > capability enabled in Syncope). The LDAP connector, specifically, only > supports that for Sun Directory Server and OpenDS / OpenDJ. > > When SYNC operation is not supported / enabled, you can only perform a > 'full reconciliation' - the difference is that with the latter all entries > are sent at every request from the external resource, while the former only > sends the delta compared to prior call. > > You can choose full reconciliation from the admin console, when editing > the resource. > > Regards. > > -- > Francesco Chicchiriccò > > ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member > http://people.apache.org/~**ilgrosso/<http://people.apache.org/%7Eilgrosso/> > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
