Okay did some research myself, I'm pretty sure that I'm just missing a little detail. I tried experimenting with trying to execute the propagation and synchronization tasks When I try to run the Propagation Task i got the following exception: org.identityconnectors.framework.common.exceptions.ConnectorException: Creation failed
When I try to synchronize i get the following exception org.quartz.JobExecutionException: While syncing on connector [See nested exception: java.lang.IllegalArgumentException: Changelog column name configuration property is empty.] Some additional info to my setup: The connector I have configured connects against a postgresql database. The resource has been tried out with the action Classes DefaultPropagationAction and LDAPMembershipPropagationActions. I tried Setting and unsetting the account link to a custom OU. None of the above configuration changes got me near to populating the LDAP with the users from the database. I should point out that, besides adding the Connector and the Resource, no changes where made to the default setup of the Standalone package. I'm wondering if I'm missing some vital detail of the Syncope concept. When adding an external resource can I really expect it to be populated to the LDAP shipped within the default package? I'm totally lost here some hints would be nice Thank you Carlo :) Am 07.06.2013 um 14:09 schrieb Giancarlo Dessena <[email protected]>: > Hello everybody, > > I have to anticipate that I'm pretty new to LDAP and Syncope, > so please forgive me if I'm not using the right wording and/or have > misunderstood some of the concepts. > > Now to my problem: > I have an external database, which contains users that have to be integrated > into LDAP. > To do achieve this i have downloaded the the Syncope standalone package. > I have already setup a DB Connector which seems to work fine. > In the next step I have setup a resource that uses the previously defined > connector. > In User mapping i have set the Account link to 'uid=' + username + > ',ou=people,o=bk' > but when reloading the ldap tree the resource does not appear. > > Any suggestions what is going wrong here? > > > Greetings Carlo
