Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quick search return with pattern like "foo*" #17

Closed
nqb opened this issue Jan 22, 2018 · 7 comments
Closed

Quick search return with pattern like "foo*" #17

nqb opened this issue Jan 22, 2018 · 7 comments
Labels
Milestone

Comments

@nqb
Copy link
Contributor

nqb commented Jan 22, 2018

Hello,

At 2d51174, when doing a quick search with pattern like "foo*", White Pages just returns "entries found" message without results. Associated search filter (|(uid=*foo**)(cn=*foo**)(mail=*foo**))

White Pages should return same entries found with "foo" pattern.

@coudot coudot added the bug label Jan 22, 2018
@coudot coudot added this to the 0.2 milestone Jan 22, 2018
@coudot
Copy link
Member

coudot commented Jan 22, 2018

Indeed this is a bug. If no entries found, the correct error message should be displayed.

@coudot
Copy link
Member

coudot commented Jan 22, 2018

Done. The test on error number was wrong.

@coudot coudot closed this as completed Jan 22, 2018
@nqb
Copy link
Contributor Author

nqb commented Jan 29, 2018

At cfae137, message prints to the user when using pattern like "foo*" : "LDAP communication error".

To my mind, it's a "Bad search filter error". Could you override PHP LDAP error message to print a more friendly message like : "Forbidden pattern in search" ?

@nqb
Copy link
Contributor Author

nqb commented Jan 30, 2018

Currently, error message "LDAP communication error" leads users to believe a technical error on software. This implies bad reputation for White Pages. Search error message seems more accurate (i.e. Incorrect search : * not allowed).

@coudot
Copy link
Member

coudot commented Jan 31, 2018

I'm not sure that overriding PHP LDAP messages is a good idea, but it is maybe the only option. We should also see how to prevent user from doing an invalid search

@nqb
Copy link
Contributor Author

nqb commented Feb 1, 2018

#21

@coudot
Copy link
Member

coudot commented Feb 2, 2018

Fixed by #21

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants