Open Bug 100606 Opened 23 years ago Updated 2 years ago

[LDAP] [RFE] Use >1 LDAP server for autocompletion

Categories

(MailNews Core :: LDAP Integration, enhancement)

enhancement

Tracking

(Not tracked)

REOPENED

People

(Reporter: ataylor+origacct, Assigned: BenB)

References

Details

Attachments

(1 file)

The current interface allows only one LDAP directory server to be used for
address autocompletion.  A user should be complete against as many directory
servers as he or she wants.

The current interface, a single dropdown box containing all the directory server
only allows one selection.  The control could be changed to a list box like the
one used to select HTML or Plain text domains in the Send Format dialog.
There is a bug already filed on this one. Marking as dup

*** This bug has been marked as a duplicate of 70600 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Actually, this isn't a dup 70600: that's about using multiple LDAP servers with
identical data for failover.  This is about completing against multiple
different LDAP servers simultaneously (eg corporate, mozilla.org, personal). 
This shouldn't be hard to do, as the architecture was designed to allow for
this.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Confirming and taking.
Assignee: srilatha → dmose
Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → ASSIGNED
Target Milestone: --- → Future
*** Bug 154017 has been marked as a duplicate of this bug. ***
Blocks: 17880
QA Contact: yulian → gchan
Is someone working on fixing that? That is exectly what we need...

Regards,
Torsten Werner
*** Bug 252654 has been marked as a duplicate of this bug. ***
Following is what we're doing to send an encrypted message to two
people listed in two different directories.  Is this the best way
to work around this limitation, or is there an easier way?

1.  Start composing message
2.  Select Security > Encrypt this message
3.  Edit > Preferences and change default autocomplete LDAP server
        to "server 2"
4.  Auto-complete addressee of first person who is listed in server 2
5.  Click on Security button to force first certificate to be pulled
       from server 2
6.  Edit > Preferences and change default LDAP server back to LDAP server 1
7.  Auto-complete addressee of second person who is listed in the main server
8.  Finish composing and send message (certificate for second addressee
        will be pulled from LDAP server 1 at this point)
-> me, I plan to work on this
Assignee: dmose → ben.bucksch
Status: ASSIGNED → NEW
Target Milestone: Future → ---
Product: MailNews → Core
BenB: are you still working on this?  I'd be interested in seeing it land in the
Thunderbird 1.1 timeframe...
In general yes, but not since we last talked about it. Busy with a release and
real life.

I have the changes to MsgComposerCommands.js (or similar), made it add one
autocomplete source per server, but I still see only one in the widget. No idea
why or how to find out.

I can attach my changes, if you want to take a look.
FWIW, here's my current work. It *should* work as-is, but it doesn't work, and
I have no idea why. I'm adding multiple "sessions" (one per server) to the
autocomplete widget, and they seem to get added and names uniquely in the
autocomplete's internal list. But only one is used. I couldn't find an obivous
limitation in the autocomplete widget that would be causing that.

Any useful help or hint on that is appreciated.

I deliberately hardcoded the list of server names. Making a pref out of that
should be trivial:
-	 var directories = ["ldap_2.servers.UW", "ldap_2.servers.novell"];
+	 var directories = pref.getChar("ldap_2.servers.list").split(",");
or similar.
Essentially the same as bug 125188 which covers slightly more and has more up to date patches. Therefore duping to that bug.
Status: NEW → RESOLVED
Closed: 23 years ago17 years ago
QA Contact: grylchan → ldap-integration
Resolution: --- → DUPLICATE
Product: Core → MailNews Core
Undupping, because 125188 is later, less specific, and the patches did not move forward, and this bug here has patches, too.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
What version of Thunderbird will this fix be in?
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: