Issue #110 has been updated by Jonathan Clarke. Category set to Core Assigned to set to Jonathan Clarke Target version set to 1.1.0
OK, I've reproduced this issue. Source and destination beans are not constructed in the same way, even if they are both LDAP. For the destination bean, all values are just read in and never modified. For the source bean, we attempt to match typing. J?r?me corrected a bug similar to this, for binary types, but this doesn't seem to apply to multi-valued attributes. Investigating a fix... ---------------------------------------- Bug #110: userPassword is always modified http://tools.lsc-project.org/issues/show/110 Author: Cl?ment Oudot Status: New Priority: Normal Assigned to: Jonathan Clarke Category: Core Target version: 1.1.0 Hi, just updated my connector and I see that my attribute userPassword is always updated, which is strange because it is in clear text (SASL) and the same in source and destination. The config is: <pre> lsc.syncoptions.user = org.lsc.beans.syncoptions.PropertiesBasedSyncOptions lsc.syncoptions.user.default.action = F # userPassword <- sAMAccountName lsc.syncoptions.user.userPassword.default_value = "{SASL}" + srcBean.getAttributeValueById("sAMAccountName") + "@example.com" </pre> userPassword is declared in lsc.tasks.user.dstService.attrs Do you have an idea? -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.lsc-project.org/pipermail/lsc-dev/attachments/20090717/034d9bc0/attachment.htm>
