Closed Bug 277707 Opened 20 years ago Closed 20 years ago

Auto complete for address fails with LDAP initalisaztion problem

Categories

(MailNews Core :: LDAP Integration, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: MartinSGill, Assigned: sspitzer)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Auto complete for address fails with LDAP initalisaztion problem, yet going into contacts and searching for the same name returns a valid result. Reproducible: Always Steps to Reproduce: 1. Go to to field, start typing a name 2. see LDAP problem message in drop down 3. click contacts 4. select LDAP address book 5. type same thing into search for field 6. See correct result returned. Actual Results: See above. Expected Results: See above
-> Core:MailNews:LDAP Integration
Assignee: mscott → sspitzer
Component: Address Book → MailNews: LDAP Integration
Product: Thunderbird → Core
QA Contact: grylchan
Version: unspecified → Trunk
Martin: Are you able to provide details for: 1. Go to a field (which field specifically), type what (exact name please) Any ldap error logs you have
I'm afraid I cannot give you those detials anymore. I completely rebuilt my ldap service from scratch and I don't have the problem anymore. I am using a much simpler authentication system at the moment, (i.e. not very secure) so that might have been what resolved it. If I run into the problem again once I start locking down the ldap security i'll post it here. It seems as though the method used to authenticate a user in thunderbird is different depending on how you try to access the LDAP server. One other thing to note is that I now no longer connect to the LDAP server using SSL.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
(In reply to comment #3) > I'm afraid I cannot give you those detials anymore. > > I completely rebuilt my ldap service from scratch and I don't have the problem > anymore. Based on reporters comment, marking as WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.