Alright, I have removed all configurations pertaining 'uid', the actual 
attribute is now canonically 'sAMAccountName' and the only occurrence of 'uid' 
is now in ibatis when it is working on the actual column of the table. FWIW, 
'uid' is present in the AD and is actually the same value as 'sAMAccountName' 
but for some reason, I wasn't able to sync at all with 'uid' being the 
pivot-attribute.

Anyway, for some reason, the attribute 'sn'/'Name' is still not forced by the 
current configuration.

Thanks for your help, as always!

-----Ursprüngliche Nachricht-----
Von: lsc-users <[email protected]> Im Auftrag von Clément 
OUDOT
Gesendet: Montag, 6. Mai 2019 15:22
An: [email protected]
Betreff: Re: [lsc-users] LDAP -> MySQL-Synchronization: Not Updating Fields 
despite Difference


Le 06/05/2019 à 13:01, Alexander Herr a écrit :
> I am trying to set up an LDAP (well, AD actually) to MySQL synchronization. 
> I've managed for the system to recognize missing entries and the 
> <create>-SQL-statement is successfully run. But I am having problems with 
> getting Update-on-Difference working.


It seems that you have some garbage between uid/samaccountname attributes. If 
uid does not exists in source, then do not set it in source fetched attribute. 
On the same idea, if you map in destination uid with samaccountname with SQL 
'as' keywork, then don't use uid in lsc.xml, just use samaccountname. Do the 
mapping in lsc.xml or in ibatis, not in both files.


--
Clément Oudot | Identity Solutions Manager

[email protected]

Worteks | https://www.worteks.com

_______________________________________________________________
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
_______________________________________________________________
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

Reply via email to