Bug #63
closed
Complex LDAP substring filter failure
Added by Jörg Ebeling over 1 year ago.
Updated about 1 year ago.
Description
Complex LDAP substring filter like (telephoneNumber=*1*2*3*), like used by Mitel OIP's, don't get interpreted correctly
Files
- Status changed from New to In Progress
- % Done changed from 0 to 10
Found the failure within a library included from my used LDAP server module.
So it's double complicated.
Will take 2-5 days more to check how it's fixable :-/
I'm sorry for the delay.
- % Done changed from 10 to 40
Fixed LDAP-Servers subAny Parser, but found another failure with subInit+subAny.
Guess subFinal will also have an issue.
After a couple of work around some SubstringFilter bugs, of the used LDAP-Server module, decided to switch to another asn1-ber library which look pretty good now.
- Status changed from Feedback to Closed
Also available in: Atom
PDF
Go to top
Updated by