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 persist.
17:59:07.175 DEBUG
org.connid.bundles.db.table.DatabaseTableConnector.getLatestSyncToken New token
value 1,351,187,890
17:59:07.175 DEBUG
org.connid.bundles.db.table.DatabaseTableConnector.getLatestSyncToken
getLatestSyncToken
17:59:07.175 INFO
org.connid.bundles.db.table.DatabaseTableConnector.getLatestSyncToken commit
getLatestSyncToken
17:59:07.176 DEBUG
org.connid.bundles.db.table.DatabaseTableConnector.getLatestSyncToken
getLatestSyncToken commited
17:59:07.176 DEBUG
org.identityconnectors.framework.api.operations.SyncApiOp.getLatestSyncToken
Return: SyncToken: 1351187890
17:59:07.225 DEBUG
org.identityconnectors.framework.api.operations.ValidateApiOp.validate Enter:
validate()
17:59:07.227 INFO
org.connid.bundles.db.table.DatabaseTableConfiguration.validate Validate
DatabaseTableConfiguration
17:59:07.227 INFO
org.connid.bundles.db.table.DatabaseTableConfiguration.validate Validate driver
configuration.
17:59:07.227 DEBUG
org.connid.bundles.db.table.DatabaseTableConfiguration.validate Driver
configuration is ok
17:59:07.227 DEBUG
org.connid.bundles.db.table.DatabaseTableConfiguration.validate Configuration
is valid
-- correct a null value here ? -->> 17:59:07.227 DEBUG
org.identityconnectors.framework.api.operations.ValidateApiOp.validate Return:
null
17:59:57.594 DEBUG
org.identityconnectors.framework.api.operations.GetApiOp.getObject Enter:
getObject(ObjectClass: __ACCOUNT__, Attribute: {Name=__UID__, Value=[denis]},
OperationOptions: {ATTRS_TO_GET:[]})
17:59:57.595 INFO
org.connid.bundles.db.table.DatabaseTableConnector.checkAlive checkAlive
DatabaseTable connector
Do you have any suggestion ?
Thanks,
Denis.
-----Messaggio originale-----
Da: Francesco Chicchiriccò [mailto:[email protected]]
Inviato: martedì 23 ottobre 2012 17:21
A: [email protected]
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 users
> 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
http://people.apache.org/~ilgrosso/
