Passing username information to the next-hop firewall

Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems

Moderator: Qbik Staff

Passing username information to the next-hop firewall

Postby larianto » Oct 10 17 9:38 pm

Hello... We are currently testing a configuration in an Active Directory environment where WinGate is installed between our internal users and the firewall. The firewall also performs URL filtering function and needs to be able to identify users to correctly apply various URL filtering rules. The firewall does not have the capability to be configured as an upstream proxy. Is there a way to configure WinGate to pass the username information to the firewall? Thank you!
larianto
 
Posts: 1
Joined: Oct 10 17 9:11 pm

Re: Passing username information to the next-hop firewall

Postby adrien » Oct 11 17 8:37 am

You can add headers to the upstream request, e.g use a flow-chart policy on the Request event of the proxy with some script like

Request.Headers.Add("X-For-User", User.AccountName)

or

Request.Headers.Add("X-Forwarded-For", Session.ClientIp)



but you would probably want to stop that leaking past your next firewall, can it strip headers?
adrien
Qbik Staff
 
Posts: 5212
Joined: Sep 03 03 2:54 pm
Location: Auckland


Return to WinGate

Who is online

Users browsing this forum: Bing [Bot] and 3 guests

cron