LDAP server preferences have no username/password provision

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Address Book & Contacts
RESOLVED EXPIRED
15 years ago
8 years ago

People

(Reporter: Ian Beyer, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031030
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031030

When setting up an LDAP server in the Address Book, there's no provision for a
username/password login. 

Reproducible: Always

Steps to Reproduce:
1.
2.
3.



Expected Results:  
Have an option to include username and password for LDAP server login.

Comment 1

15 years ago
-> MailNews

There is a Bind DN field, isn't there?
Assignee: MarkCSmithWork → sspitzer
Component: LDAP Tools → Address Book
Product: Directory → MailNews
QA Contact: nbaca
Version: other → Trunk
Mark, there sure is, but it's not implemented to the spec.

See http://www.mozilla.org/mailnews/specs/addressbook/#Directory

Dan, do you have time to do this?
Blocks: 148891
*** Bug 235233 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey

Comment 4

14 years ago
The Bind DN field confusion is documented in bug 166869, which I found and
commented in prior to finding this bug.

Updated

13 years ago
Assignee: sspitzer → mail
QA Contact: nbaca → addressbook

Comment 5

9 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 6

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.