new responder policy that Citrix supplied applies ...
# citrix-netscaler
c
new responder policy that Citrix supplied applies to all vservers not just vservers using saml. fun, I guess because all endpoints have those url paths even if saml is not configured.
e
Can you send me the case number where that was provided?
c
The case number for the support ticket I opened for this issue is 101937533.
j
Very interesting?!
Eric, can you just share if it's highly recommended to upgrade to the 5d version of the policy when I just deployed 5c success this morning? Without any details, for sure. That would be very helpful. Thank you.
n
When you say all vservers, does that mean if SAML is defined “somewhere” in the config of the appliance or its now also impacting systems with no saml config?
e
We haven't expanded the impact beyond those two vserver types.
👍 1
c
From Citrix support “ thank you Yes please apply to  all vpn and all auth vservers”, the same is also stated in policy they sent over.
j
In 5d in Notes, there is NOT the recommendation you've mentioned (not in mine!) Now I'm confused
c
This was the line in the attachment they sent over in the v5d policy that made me question it, so I replied and their tech support replied with the above. I had directly asked "Thank you, this appears to apply to all vservers and not just those vservers utilizing SAML auth, correct?"
k
Great info. Thanks!
j
does 5d still have the NDA?
i did 5c this morning, took kids to their activities came back to this chat to see there is a 5d
why can't our TAMs send us the responder policies
waiting on support now
got rebooted on a pair that is on 5c -- I saw no hits on the policy on this pair
n
Seems like Mike Streetz is having the same issue, yeah. Trying to hunt down the specific IP's that they're coming from.
j
what is the process to block the IPs on the netscaler
are you guys unbinding the other policy or mucking with the priority?