Closed
Bug 309400
Opened 19 years ago
Closed 19 years ago
LDAP attribute map only allows a maximum of one attribute to be zero-length
Categories
(MailNews Core :: LDAP Integration, defect)
MailNews Core
LDAP Integration
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dmosedale, Assigned: dmosedale)
Details
(Keywords: fixed1.8)
Attachments
(1 file)
715 bytes,
patch
|
Bienvenu
:
review+
Bienvenu
:
superreview+
asa
:
approval1.8b5+
|
Details | Diff | Splinter Review |
This is wrong and causes a set of use cases of ldap attribute map code to fail. Patch forthcoming.
Assignee | ||
Comment 1•19 years ago
|
||
Explicitly don't check for multiple null-valued attribute-lists when sanity checking an attribute map.
Assignee | ||
Updated•19 years ago
|
Attachment #196855 -
Flags: superreview?(bienvenu)
Attachment #196855 -
Flags: review?(bienvenu)
Updated•19 years ago
|
Attachment #196855 -
Flags: superreview?(bienvenu)
Attachment #196855 -
Flags: superreview+
Attachment #196855 -
Flags: review?(bienvenu)
Attachment #196855 -
Flags: review+
Assignee | ||
Comment 2•19 years ago
|
||
Fixed on the trunk. Requesting approval for the 1.8 branch, as this bug severely curtails the usability of the LDAP attribute map, and the fix is low risk.
Status: NEW → RESOLVED
Closed: 19 years ago
Flags: blocking1.8b5?
Resolution: --- → FIXED
Updated•19 years ago
|
Attachment #196855 -
Flags: approval1.8b5+
Updated•19 years ago
|
Flags: blocking1.8b5? → blocking1.8b5+
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•