Hi Sébastien,

On 6/22/2012 3:41 AM, Sébastien Bahloul wrote:
Hi Roy,

First, try to switch on the 2.0 branch because the 1.2 is quite old.

OK! I have 2.0rc2 running now. My new lsc.xml file is at http://pastebin.com/nQZt6SVB . The XML persistence map is unchanged.

Still getting similar error though:
# lsc -f /etc/lsc -s all -n
Jun 22 17:49:03 - DEBUG - Loading XML configuration from: /etc/lsc/lsc.xml
Jun 22 17:49:04 - INFO - Logging configuration successfully loaded from /etc/lsc/logback.xml Jun 22 17:49:04 - INFO - LSC configuration successfully loaded from /etc/lsc/ Jun 22 17:49:04 - INFO - Connecting to LDAP server ldap://dc1.example.net:389/DC=example,DC=net as CN=lscsync,CN=Users,DC=example,DC=net Jun 22 17:49:04 - DEBUG - Reading sql-map-config.xml from file:/etc/lsc/sql-map-config.xml Jun 22 17:49:04 - WARN - No clean request has been specified for task=syncPasswords. During the clean phase, LSC wouldn't be able to get the right entries and may delete all destination entries !
Jun 22 17:49:04 - INFO  - Starting sync for syncPasswords
Jun 22 17:49:04 - DEBUG - Synchronizing syncPasswords for {uid=adent}
Jun 22 17:49:04 - ERROR - Unable to get object for id=adent
Jun 22 17:49:04 - ERROR - All entries: 1, to modify entries: 0, modified entries: 0, errors: 1

On 6/22/2012 11:06 AM, Sébastien Bahloul wrote:
OK. Can you try to switch
from
lsc.tasks.pg2ad_pw.dstService.pivotAttrs = uid
to
lsc.tasks.pg2ad_pw.dstService.pivotAttrs = samAccountName

I did try samAccountName in <pivotAttributes> but I see no change. I also tried using the "description" field for the destination (just in case this is an Active Directory password attribute issue). Alas same error still.

Thanks for your help so far.  Bon week-end à vous.

--
Roy McMorran
Systems Administrator
MDI Biological Laboratory
[email protected]


_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org

lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users

Reply via email to