Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 34,895
    • Issues 34,895
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,211
    • Merge Requests 1,211
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #139

Closed
Open
Opened Dec 22, 2015 by Drew Blessing@dblessingMaintainer

Support LDAP Failover?

Zendesk issue: https://gitlab.zendesk.com/agent/tickets/13921

A customer was under the impression that support for multiple LDAP servers meant that if one stopped responding the users would still be able to sign in via the secondary. I can see how this would appear possible.

Can we support failover? How might that look?

cc/ @rdavila @dbalexandre Do you have any idea?

Edited Sep 02, 2020 by 🤖 GitLab Bot 🤖
Assignee
Assign to
Next 3-4 releases
Milestone
Next 3-4 releases
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#139