LDAP attribute map only allows a maximum of one attribute to be zero-length

RESOLVED FIXED

Status

MailNews Core
LDAP Integration
RESOLVED FIXED
12 years ago
9 years ago

People

(Reporter: dmose, Assigned: dmose)

Tracking

({fixed1.8})

Trunk
fixed1.8
Bug Flags:
blocking1.8b5 +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

12 years ago
This is wrong and causes a set of use cases of ldap attribute map code to fail.
 Patch forthcoming.
(Assignee)

Comment 1

12 years ago
Created attachment 196855 [details] [diff] [review]
patch, v1

Explicitly don't check for multiple null-valued attribute-lists when sanity
checking an attribute map.
(Assignee)

Updated

12 years ago
Attachment #196855 - Flags: superreview?(bienvenu)
Attachment #196855 - Flags: review?(bienvenu)

Updated

12 years ago
Attachment #196855 - Flags: superreview?(bienvenu)
Attachment #196855 - Flags: superreview+
Attachment #196855 - Flags: review?(bienvenu)
Attachment #196855 - Flags: review+
(Assignee)

Comment 2

12 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
Last Resolved: 12 years ago
Flags: blocking1.8b5?
Resolution: --- → FIXED

Updated

12 years ago
Attachment #196855 - Flags: approval1.8b5+

Updated

12 years ago
Flags: blocking1.8b5? → blocking1.8b5+
(Assignee)

Updated

12 years ago
Keywords: fixed1.8
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.