Issue #152 has been updated by Jonathan Clarke.

Status changed from Assigned to Closed
% Done changed from 0 to 100


----------------------------------------
Bug #152: Add and modify operations do not handle empty fields the same way
http://tools.lsc-project.org/issues/show/152

Author: Jonathan Clarke
Status: Closed
Priority: Normal
Assigned to: Jonathan Clarke
Category: Core
Target version: 1.1.2


Consider a db2ldap synchronization task, which selects from a field in the 
source the empty string: "".

In the case of modifying an existing entry in the destination, this field is 
simply ignored, considering that empty string is equivalent to no value. (This 
is not strictly true in LDAP, as pointed out by Raphaël and Clément, but is 
necessary for some attribute syntaxes including Directory String).

In the case of adding a new entry to the destination, LSC attempts to add this 
field with an empty value, eg:
add: street
street: 

This fails in most cases. I am therefore fixing the 1.1 branch to ignore empty 
values in add in the same way they are already ignored for modifications.


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

Reply via email to