You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "fabio martelli (JIRA)" <ji...@apache.org> on 2016/03/23 15:37:25 UTC

[jira] [Created] (SYNCOPE-800) Synchronization fails in case of accountId mapped on derived attribute starting with literal

fabio martelli created SYNCOPE-800:
--------------------------------------

             Summary: Synchronization fails in case of accountId mapped on derived attribute starting with literal
                 Key: SYNCOPE-800
                 URL: https://issues.apache.org/jira/browse/SYNCOPE-800
             Project: Syncope
          Issue Type: Bug
          Components: core
    Affects Versions: 2.0.0-M1, 1.2.7
            Reporter: fabio martelli
             Fix For: 1.2.8, 2.0.0


Synchronization fails in case of synchronized resource maps accountId on a derived attribute starting with a literal.

See [1] for details.

The bug is into AbstractSubjectDAOImpl.split() method: empty tokens have to be discarded.
Be sure to make SyncUtilities.findExisting() method more robust to JPA exceptions due to bad queries.

[1] http://syncope-user.1051894.n5.nabble.com/LDAP-synchronisation-and-User-derived-attribute-as-account-ID-with-database-resource-tp5708357p5708390.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)