IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-7017

Support load-balanced LDAP/AD servers with FishEye/ Crucible

    • 11
    • 16
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      FishEye/ Crucible does not currently support connecting to load-balanced AD servers.

      Synchronising between AD servers is not supported. Microsoft Active Directory does not replicate the uSNChanged attribute across instances. For that reason, we do not support connecting to different AD servers for synchronisation.

      Many companies have a single DNS entry (mydomain.mycompany.com) that points to a load balancer that directs traffic to one of many directory servers. (Or, some companies might use DNS round robin.) However, neither the use of DNS round robin nor use of an actual load balancer is supported by FishEye/ Crucible – both approaches to load balancing direct traffic to different servers, which would violate limitation #2 above.
      Currently, FishEye/ Crucible only supports connecting to a single directory server, not different (load-balanced) servers.

      Suggested Solution

      Add support for load-balanced LDAP/AD.

      Workaround

      Connect to a single LDAP server.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'FishEye'
            1. FishEye
            2. FE-7017

            Support load-balanced LDAP/AD servers with FishEye/ Crucible

              • 11
              • 16
              • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

                Problem Definition

                FishEye/ Crucible does not currently support connecting to load-balanced AD servers.

                Synchronising between AD servers is not supported. Microsoft Active Directory does not replicate the uSNChanged attribute across instances. For that reason, we do not support connecting to different AD servers for synchronisation.

                Many companies have a single DNS entry (mydomain.mycompany.com) that points to a load balancer that directs traffic to one of many directory servers. (Or, some companies might use DNS round robin.) However, neither the use of DNS round robin nor use of an actual load balancer is supported by FishEye/ Crucible – both approaches to load balancing direct traffic to different servers, which would violate limitation #2 above.
                Currently, FishEye/ Crucible only supports connecting to a single directory server, not different (load-balanced) servers.

                Suggested Solution

                Add support for load-balanced LDAP/AD.

                Workaround

                Connect to a single LDAP server.

                        Unassigned Unassigned
                        bstuart Ben Stuart (Inactive)
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            bstuart Ben Stuart (Inactive)
                            Votes:
                            0 Vote for this issue
                            Watchers:
                            1 Start watching this issue

                              Created:
                              Updated: