Issue #110 has been updated by Jonathan Clarke.
Cl?ment Oudot wrote: > > (note the force_value instead of default_value - I think you can't be > > reading userPassword from your source.) > > Ture, I build userPassword value in lsc.properties. So what should be used, > force_value or default_value? Using default_value will only write the attribute to the destination if there is not already a value for that attribute. So if userPassword contains, for example "secret", it will never be updated by a default_value. However, force_value makes sure to force the destination attribute to the value you want. Jon ---------------------------------------- Bug #110: userPassword is always modified http://tools.lsc-project.org/issues/show/110 Author: Cl?ment Oudot Status: Assigned 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/20090720/1a3783b9/attachment.htm>
