I am using two AD domains, yes. The credentials are able to read the attributes. The source binddn is the same one I have been using for all of my testing. I am running against a different destination AD now, but the problem here appears to be source-side.
On Wed, May 16, 2012 at 8:46 AM, Clément OUDOT <[email protected]> wrote: > 2012/5/16 Hugh Kelley <[email protected]>: > > I had run it both ways, KEEP and FORCE. The result was/is the same. See > > below: > > > > dn: CN=Gwen Young,OU=Users,OU=US Scottsdale,dc=xyz,dc=qa1 > > changetype: add > > unicodePwd:: IgAxAHEAYQB6ACEAUQBBAFoAIgA= > > > > Are you syncrhonizing 2 active directory servers? I see sAmAccountName > in source and destination attribute... > > Then, are you sure that the binddn used in the <connection> can read > all attributes in source and destination? >
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
