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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.7, 2.0.0-M1
• Fix Version/s: 1.2.8, 2.0.0-M3
• Component/s: core
• Assignee: Fabio Martelli
• Reporter: Fabio Martelli
• Created: 23/Mar/16 14:37
• Updated: 03/Jun/16 06:18
• Resolved: 29/Mar/16 10:02

Description

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