Hi,
FYI [1] have been solved.
Best regards,
Andrea
[1] https://issues.apache.org/jira/browse/SYNCOPE-1345
Il 24/07/2018 13:09, Andrea Patricelli ha scritto:
Hi,
thanks for all the info provided. I confirm that there is a bug in the
application.
I opened an issue about this [1].
Best
Hi,
thanks for all the info provided. I confirm that there is a bug in the
application.
I opened an issue about this [1].
Best regards,
Andrea
[1] https://issues.apache.org/jira/browse/SYNCOPE-1343
Il 24/07/2018 11:42, indhupriya ha scritto:
Hi Andrea,
I am using db-table connector for
Hi Andrea,
I am using db-table connector for connecting to MySQL and 'ad' connector for
active directory connection.
The same issue exist in both cases.
Thanks,
Indhupriya.S
--
Sent from: http://syncope-user.1051894.n5.nabble.com/
Ok,
thanks for the info. Which connector are you using? db-scripted or db-table?
Best regards,
Andrea
Il 24/07/2018 08:25, indhupriya ha scritto:
Hi Andrea,
Thanks for the quick turn around.
The syncope version we are using is 2.0.2 and Yes, We have confirmed that
the other modified fields
Hi Andrea,
Thanks for the quick turn around.
The syncope version we are using is 2.0.2 and Yes, We have confirmed that
the other modified fields (with values) are updated in Syncope and only the
fields which are modified as 'NULL' is not getting updated during PULL task
from external resource.
Hi Indhupriya,
which version of Syncope are you running?
Do you confirm that other fields (with values) are correctly updated?
Best regards,
Andrea
Il 23/07/2018 15:10, indhupriya ha scritto:
Hi,
When an existing field is updated as "Null" in external resource such as
"LDAP or MySQL", PULL
Hi,
When an existing field is updated as "Null" in external resource such as
"LDAP or MySQL", PULL task is not changing the field as 'NULL' in Syncope
and retain the deleted field content. But, when a field is edited to some
other value, the changed value is updated. Is there a way to update the
