Denis Signoretto created SYNCOPE-230:
----------------------------------------
Summary: Sync user attributes using a long schema attribute as
accountId
Key: SYNCOPE-230
URL: https://issues.apache.org/jira/browse/SYNCOPE-230
Project: Syncope
Issue Type: Bug
Components: core
Affects Versions: 1.0.2-incubating
Environment: Linux CentOs x86_64, Oracle 10g, Apache Tomcat 7.0.26,
Java(TM) SE Runtime Environment (build 1.6.0_31-b04)- Java HotSpot(TM) 64-Bit
Server VM
Reporter: Denis Signoretto
Synching 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.
Definig the same attribue as "Long" the sync task don't works.
After deletions of all users, redefining the attribute in Sycope as Long,
forced a Reset Token on external resource, the sync don't match on the
attribute and no update operation occur.
As requested I'll attach:
1. the external DB schema: it's DB VIEW so I'll attach desc command result
2. the DBTable connector configuration
3. the DB resource mapping
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
