Skip to main content

LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

HOWTO: Authenticating requests based on X-Forwarded-For

Expand / Collapse


This article applies to:

  • WebMarshal 7.5.0 and above

Question:

  • How do I apply IP authentication based on the X-Forwarded-For header of a request?

Procedure:

WebMarshal IP Authentication normally evaluates the connecting IP address.

You can configure WebMarshal to authenticate based on the X-Forwarded-For header included in the request. 

This option allows you to authenticate and apply policy based on the client IP address where the requests pass through a load balancer or other device before reaching WebMarshal.

WebMarshal considers only the first IP address in the first valid X-Forwarded-For header.

To configure X-Forwarded-For evaluation:

  1. Create one or more WebMarshal IP Groups that include the IP addresses of the original clients. 
  2. To configure the trusted sources of forwarded requests (such as load balancers), add entries to the WebMarshal Proxy Configuration file (WMProxy.config.xml) on each processing server
    • The XFFEntry range should only include the load balancer IP addresses, not the client IP addresses
    • Most installations will have only one XFFEntry element, but you can include more than one XFFEntry element if necessary
    • Include quote marks but not braces
    <WebMarshal>
    <Proxy>
    <Config>

    <XFF enabled="true" >
    <XFFEntry from="{IPaddressStart}" to="{IPaddressEnd}" />
    </XFF>
    </Config>
    </Proxy>
    </WebMarshal>
  3. Restart the WebMarshal Proxy service.

Note

  • WMProxy.config.xml will include other entries. Do not change the other entries.
  • XML files are case sensitive.
  • For general information about editing XML settings files, see article Q12705.

To contact LevelBlue about this article or to request support:


Rate this Article:
     

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.