[DOCS-15027] X-Forwarded-for should be marked as requirement for configuring Ops manager in High Availability Created: 12/Jan/22  Updated: 28/Feb/22  Resolved: 27/Jan/22

Status: Closed
Project: Documentation
Component/s: Automation Agent, Ops Manager
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Vinay Gahlout (Inactive) Assignee: James Sanchez (Inactive)
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
DOCS-15101 Backport DOCSP-15027 to v5.0 Sub-task Closed James Sanchez  
DOCS-15102 Backport DOCSP-15027 to v4.4 Sub-task Closed James Sanchez  
Participants:
Days since reply: 1 year, 49 weeks, 2 days ago
Epic Link: DOCS: 4.4 Server Release Work

 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 ? 

 



 Comments   
Comment by Githook User [ 28/Feb/22 ]

Author:

{'name': 'mongodbchez', 'email': '90717131+mongodbchez@users.noreply.github.com', 'username': 'mongodbchez'}

Message: DOCS-15027 Clarify x-forwarded-for header as requirement for OM in HA (#4209)

  • DOCS-15027 Clarify x-forwarded-for header as requirement for OM in HA
  • Rephrase 2nd bullet point
  • add note on workaround
Comment by Githook User [ 10/Feb/22 ]

Author:

{'name': 'mongodbchez', 'email': '90717131+mongodbchez@users.noreply.github.com', 'username': 'mongodbchez'}

Message: Backport DOCSP-15027 to v5.0

  • DOCS-15027 Clarify x-forwarded-for header as requirement for OM in HA
  • Rephrase 2nd bullet point
  • add note on workaround
Comment by Githook User [ 10/Feb/22 ]

Author:

{'name': 'mongodbchez', 'email': '90717131+mongodbchez@users.noreply.github.com', 'username': 'mongodbchez'}

Message: Backport DOCSP-15027 to v5.0

  • DOCS-15027 Clarify x-forwarded-for header as requirement for OM in HA
  • Rephrase 2nd bullet point
  • add note on workaround
Comment by Githook User [ 27/Jan/22 ]

Author:

{'name': 'mongodbchez', 'email': '90717131+mongodbchez@users.noreply.github.com', 'username': 'mongodbchez'}

Message: DOCS-15027 Clarify x-forwarded-for header as requirement for OM in HA (#4209)

  • DOCS-15027 Clarify x-forwarded-for header as requirement for OM in HA
  • Rephrase 2nd bullet point
  • add note on workaround
Comment by James Sanchez (Inactive) [ 13/Jan/22 ]

Hi vinay.gahlout could you please tech review the PR for this update when you have a moment https://github.com/10gen/mms-docs/pull/4209? If you'd like to have someone else do the tech review, please LMK. Thank you.

Generated at Thu Feb 08 08:11:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.