On 23/01/2017 13:30, Martin van Es wrote:
Hi,
Finally, I've taken the time and went ahead (re)installing Syncope to
try and play with 2.0.
First: it's a nice improvement (on the admin interface). Well done!
Thanks! :-)
Also glad for your enduring interest in Apache Syncope.
I've (re) created my test LDAP connector and am able to
provision/activate/enable/disable users and groups/groupMembership
from admin console.
Now I'd like to emulate an authoritative source connector (e.g. HR)
from CSVDir connector. I supply five columns in this file called
id,email,sn,status and delete. I inserted a header line designating
these columns and exactly one test account as 2nd line. Values are
separated by comma's.
I created the connector and resource to follow the columnames/order in
my file, but when I try to setup user provision rules, two thing
surprise me:
I can't select target columns that are designated for key, status and
delete by the connector. Is this by-design?
As far as I can read from the class implementing the ConnId SCHEMA
operation (e.g. the one that it is used to populate that Admin UI
autocomplete text fields):
https://github.com/Tirasa/ConnIdCSVDirBundle/blob/master/src/main/java/net/tirasa/connid/bundles/csvdir/methods/CSVDirSchema.java#L65
I think it is somewhat by design, but I am not sure it is for good; for
the moment, please use:
* __NAME__ as value for key column
* __ENABLE__ as value for status column (you should not need to provide
a mapping for this, though, as it is done automatically)
The delete column seems to be reserved for internal usage.
Second, when I finish the provisioning rules (mapping surname to sn
and email to email, because that's all that's available on target) by
clicking "Save" in the last dialog, Syncope fails with error: "Unable
to find property: 'connObjectKeyValidation'. Locale: null, style:
null"
The message you should get is "There must be exactly one AccountId",
which is anyway bad as 'AccountId' (up to 1_2_X) is now (from 2_0_X)
ConnObjectKey instead.
It complains that there must be exactly one mapping flagged as 'Remote key'.
I am able to replicate your error, please file an issue for this.
Regards.
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/
