Closed Bug 156343 Opened 23 years ago Closed 23 years ago

[LDAP] address lookup appears to be case sensitive when dir server lookup is enabled

Categories

(MailNews Core :: Security: S/MIME, defect, P1)

1.0 Branch
x86
All

Tracking

(Not tracked)

VERIFIED FIXED
psm2.4

People

(Reporter: carosendahl, Assigned: KaiE)

Details

Attachments

(1 file)

If a directory server is configured for fetching encryption certificates during mail composition and the recipient name is not identical to the name in the certificate, it appears that the client is attempting to retrieve the certificate from the directory server even when the cert exists locally. example: Enable directory server lookups on the netscape global directory. Compose a mail message to JUNruh@netscape.com, encrypt, and send. Actual behavior: - If the cert doesn't exist in the local db already, a fetch will be performed and the cert will be added to the local directory. - If the cert already exists in the local db (which is the case the second time around), a fetch is still performed even though it should not be. The cert contains the email address junruh@netscape.com. Bug 130692 fixed the case sensitivity issue (i.e. JUNruh@netscape.com vs. junruh@netscape.com) and it is still fixed. The problem here is that once a dir server is enabled for lookups, the case-sensitivity code appears to be out of step with the execution logic. Expected behavior: Once the cert exists in the local db, regardless of case, there is no further need to perform a directory lookup and fetch operation.
Kai
Assignee: ssaux → kaie
Keywords: nsbeta1
Attached patch Patch v1Splinter Review
Summary: address lookup appears to be case sensitive when dir server lookup is enabled → [LDAP] address lookup appears to be case sensitive when dir server lookup is enabled
Comment on attachment 96009 [details] [diff] [review] Patch v1 r=javi
Attachment #96009 - Flags: review+
Comment on attachment 96009 [details] [diff] [review] Patch v1 sr=jag
Attachment #96009 - Flags: superreview+
fixed on trunk
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Trunk build 20020904 Windows Reopening - the browser cannot find any user in the configured directory server. Directory - nsdirectory.netscape.com base dn: dc=com look for junruh@netscape.com or kaie@netscape.com or carosendahl@netscape.com - none are found. The RTM release with the same profile finds the users.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Changed severity as directory lookup no longer appears to be working at all on the trunk.
Severity: minor → major
Keywords: nsbeta1nsbeta1+
Priority: -- → P1
Target Milestone: --- → 2.4
Keywords: regression
I have looked at the new failure. I'm closing this bug, since the new problem is caused by something else => bug 172028
Status: REOPENED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → FIXED
Regression keyword moved to new bug.
Keywords: regression
Verified on 20021007 Trunk Builds
Status: RESOLVED → VERIFIED
Product: PSM → Core
Version: psm2.3 → 1.0 Branch
Product: Core → MailNews Core
QA Contact: carosendahl → s.mime
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: