-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
5
-
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
Given the credentials and settings are all the same, in an ideal world, I would like to specify as
<host>host1|host2|host3</host>
Confluence could then try to connect to host1, failover to 2, failover to 3.
This is a single point of failure that would require a re-deployment to resolve, and could be avoided with this fix.
- is related to
-
JRACLOUD-23245 Provide a redundant hostname/IP for failover in LDAP
- Closed
-
CWD-422 Directory Failover option for an application
- Closed
-
CONFSERVER-8867 Failover Support For LDAP
- Not Being Considered
-
FE-5170 Failover Support For LDAP
- Not Being Considered
- relates to
-
BSERV-5299 Support LDAP failover
- Closed
[ID-8979] Failover Support For LDAP
Support reference count | Original: 21 | New: 5 |
Component/s | Original: Site - Users and Groups [ 46326 ] | |
Key | Original: CONFCLOUD-8867 | New: ID-8979 |
PM Reviewed | Original: 13/Feb/2009 [ 2009-02-13 ] | |
Project | Original: Confluence Cloud [ 18513 ] | New: Identity [ 16810 ] |
Component/s | New: Site - Users and Groups [ 46326 ] |
UIS | New: 1 |
Workflow | Original: JAC Suggestion Workflow [ 3427238 ] | New: JAC Suggestion Workflow 3 [ 3607409 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 2246426 ] | New: JAC Suggestion Workflow [ 3427238 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Support reference count | Original: 19 | New: 21 |
Workflow | Original: Confluence Workflow - Public Facing v3 - TEMP [ 2142134 ] | New: Confluence Workflow - Public Facing v3 [ 2246426 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 1901465 ] | New: Confluence Workflow - Public Facing v3 - TEMP [ 2142134 ] |
Workflow | Original: Confluence Workflow - Public Facing v2 [ 1807425 ] | New: Confluence Workflow - Public Facing v3 [ 1901465 ] |