Finally I've managed to free some time to look into this.
I believe I have found the root cause to this issue. One of my groups
have a name with a Scandinavian character, not to syncops liking.
I'we managed to reproduce the issue also with a vanilla installed
syncope, using the embedded ApacheDS.
Simply add the following group
dn:: Y249csOka3Ntw7ZyZ8OlcyxvdT1Hcm91cHMsbz1pc3A=
objectclass: top
objectclass: groupOfUniqueNames
cn:: csOka3Ntw7ZyZ8Olcw==
uniquemember: uid=pullFromLDAP,ou=People,o=isp
owner: uid=pullFromLDAP,ou=People,o=isp
Sync, and watch it crash and burn.
Brgds,
Jonas
On 01/07/16 11:24, Francesco Chicchiriccò wrote:
On 01/07/2016 11:17, Jonas Israelsson wrote:
Thought I'd give M4 a spin.
One connector, one resource, one pull task. With only user-mapping
everything is fine. But if also adding a group mapping (on the same
connector, resource and pull task ) I get some firework.
This puzzles me " *The field "realm" of instance
"JPAGroup[f873e8f2-3556-4c14-b3e8-f235567c14fd]" contained a null
value;*"
Should not that value come from the pull task (Destination Realm) ?
Anything changed from M3 ? I have not (yet) touched/enabled realm
provisioning.
Nothing should have changed within this respect, and test data
naturally contain resources with user and group mapping, and several
pull tasks.
Would you mind exporting and sharing your MasterContent.xml somehow?
Naturally you can remove passwords or other sensitive data.
You can do this by clicking on the top-right gear icon.
Alternatively, please report any relevant configuration for connector,
resource and pull task.
Thanks.
Regards.
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC,
CXF Committer, OpenJPA Committer, PonyMail PPMC
http://home.apache.org/~ilgrosso/
