While troubleshooting a responder policy issue on ...
# citrix-netscaler
d
While troubleshooting a responder policy issue on our NetScaler 14.1 systems I ran across this: https://support.citrix.com/s/article/CTX477121-responder-policy-not-honored-when-binding-to-netscaler-gateway-with-aaarequest-type?language=en_US The issue I was having though was that binding to the REQUEST type was not triggering, even with the rule set to 'true'. When I set the binding to AAA_REQUEST the Responder worked as expected. Can anyone explain the difference between the two bind points and why my experience would be different from the CTX article?
j
Where do you bind your policy?
d
I was working on this which I'm pretty sure I saw here in Slack first, but wasn't able to find the thread yesterday. https://www.julianjakob.com/netscaler-session-hijack-protection-with-responder/ When I bound the policy to the Gateway as a REQUEST policy, it wouldn't apply. When bound to AAA_REQUEST it works. The policy is also bound to the authentication server as an AAA_REQUEST per the article, but was never triggered.
Received the below from my Citrix team after asking them the question: Per the NS team, AAA_REQUEST policies will hit before authentication is complete, after that REQUEST policies are hit. AAA_request was created to rate limit authentication requests. Before the creation of this bind point, rate limiting policies wouldn't affect auth requests. Rate limiting could only be done for requests to the backend that's being proxied by the virtual server which is what the REQUEST bind point is for. https://docs.netscaler.com/en-us/citrix-adc/current-release/aaa-tm/citrix-adc-aaa-session-and-traffic-management/rate-limiting-with-gateway.html
j
Thanks for sharing, useful info! 🙏
👍 1
l
I can’t believe I missed this. We are having an almost similar issue. since 2/14. We added an audit message tothe responder policy to record the location of the request to the vserver it was attempting to reach. It was discovered if the audit message has the expression set to anything other than true it will not work for a vpn vserver in v14,1. v13.1 it doesn’t work at all
👍 1