Open Bug 218713 Opened 21 years ago Updated 2 years ago

Need UI to list extra failover LDAP servers

Categories

(MailNews Core :: LDAP Integration, defect)

defect

Tracking

(Not tracked)

People

(Reporter: mscott, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

This came up from a discussion in the enterprise mail space. Apparently in 4.x
there was LDAP UI for listing failover LDAP servers.

According to Darin, the LDAP SDK already supports a list of servers for failover
but we don't allow the user to configure such a list. 

Here's some additional comments from Brendan:

"all they want is to put a space-separated
list of hostnames in the UI.  That used to work, and I think Darin said the LDAP
API works on such a space-separated list.  So maybe it's just a matter of
letting the spaces through, or (if the LDAP API wants some other format),
translating via strtok or similar."
taking
Assignee: sspitzer → scott
OS: Windows XP → All
Hardware: PC → All
Whiteboard: Thunderbird0.3
David is looking into Bug #223603 which is the back end for supporting fail over
ldap servers which is partially related to this bug. Marking the dependency.

Depends on: 223603
Whiteboard: Thunderbird0.3
takig - this will be the bug for making the failover work. That other bug is
about not failing completely.
Assignee: mscott → bienvenu
actually, I guess this is the UI for making this work and bug 223603 is for
getting the backend to work. 

Yes, 4.x would just allow you to enter spaces as a host delimiter. I think for
Mozilla we'd like to have an explicit secondary host name for failover in the
UI. We can also allow space delimited hosts for those rare situations where more
than two hosts are needed.
Status: NEW → ASSIGNED
Product: MailNews → Core
Assignee: bienvenu → nobody
Status: ASSIGNED → NEW
QA Contact: grylchan → ldap-integration
bug 223603 still needs the multiple hosts piece 
Assignee: nobody → bienvenu
Product: Core → MailNews Core
Assignee: bienvenu → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.