FishEye and Crucible

ok understood about wanting to support chars, but can it at least not return entries if the text you are entering in the search surrounded by stars isn't present in the attribute?

Even though this is a new product at least both the old sun directory server and openldap do not return entries if you place this search text in a query.

Just for reference this is causing problems for a simple search page that will take a single search item and try them against several different attributes in the background for example:

'(|(cn=*doe*)(givenName=*doe*)(sn=*doe*)(telephoneNumber=*doe*))'

Thanks for looking into this!

Manuel,

I agree with you.
However, there should be 2 different behaviors of the matching rule : when strictly compliant with the international telephone number format and when accepting loose numbers.
When accepting loose numbers, I believe ignoring non digit is fine, but we might result in an error if the reduced string is empty.

One other thing that is not treated properly for example is +1 800 FLOWERS, which some expects to match with +1 800 356 9377.

Ludovic.

Hi Ludovic,

X.520, 8.2.9 defines the following for Telephone Number Substrings Match:

"The rules for matching are identical to those for caseExactSubstringsMatch, except that all hyphens and spaces are insignificant and removed during the insignificant character removal step."

So I think that ignoring all non-digit characters from the filter is not the correct behavior. But I'm not sure about that.

Best regards,
Manuel