That solved the problem. Sometimes when you stare at the same info over and over, you miss the obvious things. Thank you so much!
One (hopefully) last question. I am having to copy the submission_id to unit_db field so I can convert it from INTEGER to VARCHAR. Trying to sync the submission_id field was not working and I would get the following error: ERROR - Error while adding entry uid=user6,ou=people,dc=mydomain,dc=org in directory :javax.naming.directory.InvalidAttributeValueException: Malformed 'gnUniqueId' attribute value; remaining name 'uid=user6,ou=people’ I seemed to find quite a few people who were having this problem with database fields that were set to INTEGER. I tried changing the LDAP syntax for the destination attribute, but neither NumericString or Integer seemed to make any difference. Using SQL: update table_name set varchar_field = CAST(integer_field AS CHAR); does work to copy the data. But if I could get synchronization without this additional process, that would be a cleaner process. Thanks again for all your help, and your work on a great tool! On Jul 16, 2014, at 2:42 PM, Clément OUDOT <[email protected]> wrote: > > 2014-07-16 14:00 GMT+02:00 Brad Firestone <[email protected]>: > Thank you Clément! That did solve that error but it’s still not working > completely right. > > I have three users in the database right now. If I run lsc again after the > first sync, I get a list of all the attributes > for all the users, indicating that nothing will be modified. That makes > sense. > > But if I change the database value for userid_db from user6 to usersix, then > re-run lsc, I only see references to the other two > users and no modifications are made. But the last line does say: All > entries: 3, > If I change usersix back to user6, and then re-run, everything behaves > normally including modifications to other fields for user6. > Changing the userid_db and another field also results in no modifications > being made. > > I’ve since gone through and removed the uppercase letters from gnuniqueid > EVERYWHERE, including the getOneFilter > and the attribute and objectclass in the schema. It didn’t seem to make any > difference. > > So something is still blocking me from changing the userid_db value and > getting that to sync to OpenLDAP. Even though the > pivot is gnuniqueid. Do you have any idea if this can be made to work? > > > > Seems you prevent LSC from renaming entries, as I see this in your lsc.xml: > > <changeId>false</changeId> > > Just set it to true, then LSC will rename the entry in LDAP. > > Clément. > >
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
