Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-15027

X-Forwarded-for should be marked as requirement for configuring Ops manager in High Availability

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Minor - P4
    • Resolution: Fixed
    • None
    • None
    • None

    Description

      Hello Team,

      Context: Customer is facing issue while configuring the Ops Manager in HA(High Availability) using Load Balancer. He is using Layer-4 LoadBalancer which do not support X-Forwarded headers. 

       

      Blocker: The X-Forwarded-for is not mentioned as requirement on our documentation  page https://docs.opsmanager.mongodb.com/current/tutorial/configure-application-high-availability/#multiple-application-servers , due to which his Ops Manager HA is not able to identify source IP. In his words: 

      "mentioned" != "MUST BE CONFIGURED ON LOAD BALANCER".

      that's the reason I raised this ticket for mongo support. we missed it because it wasn't clearly described as a requirement. And, as a result, HA does not work properly.

       

      --Another point he has mentioned in his comment is that why we are relaying on non-MongoDB customer headers, why not create mongodb specific custom HTTP header for source IP of automation agent like we are using for MongoDB Service version below: 

      < X-MongoDB-Service-Version: gitHash=980038b07091a533affeaca3452736391c0df9f7; versionString=4.4.17.100.20210901T1617Z--

       

      Is it possible to mark X-forwarded-for as requirement for configuring the OPS Manager in HA ? 

       

      Attachments

        Issue Links

          Activity

            People

              james.sanchez@mongodb.com James Sanchez (Inactive)
              vinay.gahlout@mongodb.com Vinay Gahlout (Inactive)
              Githook User Githook User
              Vinay Gahlout (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                38 weeks, 5 days ago