I’m trying to use LSC to sync between an LDAP aggregator service (Optimal VIS) and AD LDS. I need to be able to maintain the correlation between accounts across DN and UPN changes. Optimal VIS maintains the Object GUID from the backend Active Directory as the object is passed through. AD LDS creates a new Object GUID and I can’t force it to use the Object GUID from VIS since it is it’s own “primary key” right?
So, the only way I can come up with to logically accomplish this is to try to store the Optimal VIS Object GUID into a schema attribute on the AD LDS side and use those two attributes as the pivot attribute. The only problem with this is that the Object GUID is binary and not a string value. According to Raphaël Ouazana on GitHub, LSC will support a binary pivot attribute (with a link to some example code)<https://github.com/lsc-project/lsc/blob/master/src/test/java/org/lsc/Ldap2LdapBinaryPivotSyncTest.java>. However, I’m not sure how to take that example code and implement that via the configuration file and sync process of LSC. At this point I have data successfully sync’ing between VIS and AD LDS using DN as the pivot attribute and all the data that I need to use is being sync’d successfully. I just need to work out how to maintain the link between accounts across name/email/upn/dn changes. Does anyone have any pointers? Thanks, Jeremy Sanders, CCIE 12332 R&S and Voice Solutions Architect http://www.teklinks.com<http://www.teklinks.com/> t: 205.314.6630 | m: 205.249.5988 Call me via video at sip:[email protected]<mailto:[email protected]> support: 877.800.8898 In the event you are unable to reach me and need immediate assistance, please call 205.314.6600 and ask for an Engineering Coordinator or follow the Auto Attendant instructions for our Automated Escalation System.
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] https://lists.lsc-project.org/cgi-bin/mailman/listinfo/lsc-users
