XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    auth-ldap (v0.10.11) - Specifying Multiple (Primary / Secondary) AD Servers under the URI field

    Scheduled Pinned Locked Moved Advanced features
    3 Posts 3 Posters 62 Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G Offline
      gcpeters4
      last edited by

      Is there a way to specify a primary and secondary Active Directory server when configuring auth-ldap?

      I've encountered situations where the specified URI (ldap://activedirectory1.domain.x.y) server isn't reachable so I'd like to be able to specify a secondary AD server using something like this:

      ldap://activedirectory1.domain.x.y, ldap://activedirectory2.domain.x.y

      Basically multiple AD servers; separated by a comma.

      Unlike the other forum post regarding Multiple AD Sources, both of these control the same domain.

      Thanks.

      I J 2 Replies Last reply Reply Quote 0
      • I Offline
        IgorGlock @gcpeters4
        last edited by

        @gcpeters4 Hi! You could use DNS round robin but it's 50/50 if it works for you. Just put ldap://domain.x.y in and try.

        1 Reply Last reply Reply Quote 0
        • J Offline
          john.c @gcpeters4
          last edited by

          @gcpeters4 said:

          Is there a way to specify a primary and secondary Active Directory server when configuring auth-ldap?

          I've encountered situations where the specified URI (ldap://activedirectory1.domain.x.y) server isn't reachable so I'd like to be able to specify a secondary AD server using something like this:

          ldap://activedirectory1.domain.x.y, ldap://activedirectory2.domain.x.y

          Basically multiple AD servers; separated by a comma.

          Unlike the other forum post regarding Multiple AD Sources, both of these control the same domain.

          Thanks.

          Another option is to setup AD clustering (clusters) with both controllers part of the same cluster. Alternatively setup an AD Failover which has a single FQDN endpoint but two members.

          Either or both of these likely to result in a single FQDN that can be fed into the plugin.

          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • First post
            Last post