syncope-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò <>
Subject Re: Problem syncing user using a Long schema attribute
Date Wed, 24 Oct 2012 12:12:10 GMT
On 23/10/2012 18:09, Denis Signoretto wrote:
> Hi Francesco,
> so did I. 
> I have deleted all users, redefined the user attribute in Syncope as Long resetted the
synchronization token of the external resource and launch a Sync Task manually, but the problem

I guess you have also updated the schema mapping for the DB resource in
order to set this Long attribute in Syncope as AccountId, right?

> 17:59:07.175 DEBUG org.connid.bundles.db.table.DatabaseTableConnector.getLatestSyncToken
New token value 1,351,187,890

This sounds strange: is this log message appearing *after* the
synchronization has actually take place or before?

> [...]
> -- correct a null value here ? -->> 17:59:07.227 DEBUG org.identityconnectors.framework.api.operations.ValidateApiOp.validate
Return: null


> [...]
> Do you have any suggestion ?
> Thanks,
> Denis.
> -----Messaggio originale-----
> Da: Francesco Chicchiriccò []
> Inviato: martedì 23 ottobre 2012 17:21
> A:
> Oggetto: Re: Problem syncing user using a Long schema attribute
> On 23/10/2012 16:31, Denis Signoretto wrote:
>> Hello,
>> I'm syncing user attributes FROM a resource TO Syncope using DBTable connector. 
>> The attribute used as "Column Key" is a number(10) (it's an Oracle DB).
>> If I define the attribute on Syncope as String it works well and when the sync starts,
>> all updated entries are found and triggered for the update. After deletions of all
>> and redefining the attribute in Sycope as Long the sync don't match on the attribute
>> and no update operation occur.
> Denis,
> I guess that what you're seeing is just the expected behavior: if your
> external resource (in Syncope) is not configured for full
> reconciliation, then Syncope will invoke the SYNC operation on the
> underlying connector that will return only entries in the DB that were
> modified AFTER last synchronization.
> After deleting all users and redefining the user attribute in Syncope as
> Long, don't forget to also reset the synchronization token of the
> external resource.
> Regards.

Francesco Chicchiriccò

ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member

View raw message