After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 271958 - Evo ignoring "search base" on LDAP address book
Evo ignoring "search base" on LDAP address book
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Contacts
2.0.x (obsolete)
Other All
: Normal major
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on: 273290
Blocks:
 
 
Reported: 2005-01-30 05:06 UTC by prensing
Modified: 2006-02-23 11:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Network trace of Evo (6.50 KB, text/plain)
2005-03-30 16:54 UTC, prensing
Details
Network trace of lbe LDAP browser (3.13 KB, text/plain)
2005-03-30 16:56 UTC, prensing
Details
Ethereal trace (4.98 KB, application/octet-stream)
2005-08-24 14:49 UTC, Paul Rensing
Details

Description prensing 2005-01-30 05:06:09 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:
I am trying to connect to an LDAP address book provided by our email
provider. I can log in OK, but I get no addresses. I monitored the network
traffic with Ethereal and found that Evo was attempting to search with the
"search base" set to NULL. In the preferences, the search base is clearly
set for this address book, but nothing I do seems to make it want to use it.

Note that the LDAP browser "lbe" has no problem with this site.

Steps to reproduce the problem:
1. Create an address book against an LDAP server with a search base
2. Open address book
3. 

Actual Results:
No addresses found. Search was attempted against "NULL" base, instead of
the provided one.

Expected Results:
Expected to get about 30 addresses.

How often does this happen? 
Always.

Additional Information:
Comment 1 Sivaiah 2005-03-30 08:04:56 UTC
i am sure evo uses ldap search base (looked at code and verified with
tests) what could have happend is initially you did not enter anything
in search base loadded ldap book and then changed the search base.
Unfortunately the changes done to ldap config does not take immediate
effect see bug 273290 . please do evolution --force-shutdown and try later 
Comment 2 Sivaiah 2005-03-30 12:10:02 UTC
assuming this because what i have written above marjking the dependecny
Comment 3 prensing 2005-03-30 16:54:06 UTC
Created attachment 45039 [details]
Network trace of Evo
Comment 4 prensing 2005-03-30 16:55:17 UTC
Well, I tried a number of things. I tried kill Evo with
"--force-shutdown". It did not help. 

I tried deleting the existing LDAP addressbook and recreating it. No good.

I am sniffing the network with Ethereal and it just does not want to
use the BaseDN in the search query.

I am attaching a couple of network dumps (in text form) from Ethereal.
"evo_ldap.txt" is what Evo does. "lbe_ldap.txt" is what the LDAP
browser "lbe" does. Hope this helps.
Comment 5 prensing 2005-03-30 16:56:15 UTC
Created attachment 45040 [details]
Network trace of lbe LDAP browser
Comment 6 Sushma Rai 2005-08-24 06:11:09 UTC
Looking at the code this should work.
well, can you use "Find possible search base' button and 
see if the search bases get listed for you?

try to kill evolution-data-server and evolution processes and
restart evolution and see if it works.

also it's better if you try this with newer version of Evolution.
Comment 7 Paul Rensing 2005-08-24 14:48:18 UTC
Well, I can't test the original bug, because we no longer use that provider. We
now have a Windows Active Directory server (oh well), but that is not working
either. I have attached an Ethereal trace of the network traffic. For some
reason, it keeps trying to log in with DN=null, even though it does log in with
my account once. Again, I have no trouble with using LBE.
Comment 8 Paul Rensing 2005-08-24 14:49:58 UTC
Created attachment 51262 [details]
Ethereal trace

Note: I manually munge this file to hide my password and our machine name, so
many of the packet checksums will be wrong.
Comment 9 André Klapper 2006-01-08 23:42:26 UTC
reopening
Comment 10 Sushma Rai 2006-01-09 06:38:43 UTC
from the dump i see that ldap bind is failing for you.
are you sure the bind DN and password are correct?

can you start evolution and e-d-s from the console and
paste the related log messages here?
Comment 11 Devashish Sharma 2006-02-14 09:48:03 UTC
Moving to NEEDINFO as per the last comment.
Comment 12 Devashish Sharma 2006-02-23 11:05:58 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!