Issue #268 has been updated by Raphaël Ouazana.
I don't think it is a good idea. It is a common case to not have all LDAP values populated. This warning would annoy users. ---------------------------------------- Feature #268: When you enable debug for your task, be more descriptive for the state of attributes. http://tools.lsc-project.org/issues/268 Author: Ronald Rudimor Status: New Priority: Low Assigned to: Category: Core Target version: trunk In came across a problem where the same task was failing for some users and for others not. I enabled all debugging and after a lot of effort i noticed that for some of my users the attributes that were not syncing had an "undefined" state. After further examination and testing i found out my problem (which was permission problem for the attributes). As far it concerns LSC I suggest that for any of the values defined in srcService.attrs that cannot be retrieved from the source a more descriptive message such as: "WARNING: Source Attribute %s cannot be read or doesn't exist. Please check if you have the appropriate permissions to read the attribute or if the value exists." -- 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
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
