Issue #642 has been updated by Raphaël Ouazana.
Status changed from New to Feedback
I am not sure it is a good idea to handle this case. Having a filter containing
{ and } characters could be legitimate.
----------------------------------------
Feature #642: warn the user if the variable {var} is not valid/defined/empty in
the filter
http://tools.lsc-project.org/issues/642
Author: Martin H
Status: Feedback
Priority: Normal
Assigned to:
Category: Core
Target version: 2.1
What about to warn the user if the variable {var} is not valid/defined/empty in
the filter (rather than putting {var} in the search string as is)
Currently, "{var}" is passed as is on the search string... I found that by
looking in my LDAP directory logs
@...filter="(&(objectClass=inetOrgPerson)(uid={uid}))"@
Additionnaly, the search above look for a user {uid} / would be strange but it
could exists.
I think it should be replaced with 'empty string' (uid=) when undefined.
--
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
