[
https://issues.apache.org/jira/browse/SYNCOPE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215762#comment-15215762
]
ASF subversion and git services commented on SYNCOPE-800:
---------------------------------------------------------
Commit 5c4181fcbe77ca2e57654b415ef5777f66f32fcd in syncope's branch
refs/heads/master from [~fmartelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=5c4181f ]
[SYNCOPE-800] fix the issue by improving findByDerAttrValue
> 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: 1.2.7, 2.0.0-M1
> Reporter: fabio martelli
> Assignee: 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)
