Now while Microsoft has had some huge announcements made at AzureCon around support for NVIDIA GRID Architecture we still to have Netscaler in place in order to be able to optimize traffic to endpoints which want to leverage this capabilities.
Introduction Since the NetScaler platform in many cases is setup as a reverse proxy, the Subnet IPs (or SNIPs) configured are used as the source address in the communication between NetScaler and Backend servers.
The last couple of months we have seen lots of versions of the NetScaler comming from Citrix development.
When you configure your Netscaler to protect a back-end website or web service and configure your Netscaler as a SAML SP.
SAML is a protocol that is taking off more and more allowing authentication of users without passwords over public Networks.
XenMobile has a secure web browser called WorxWeb that allows you to browse web pages on the internet and on your private intranet, but how to selectively redirect this web traffic to a proxy server?
NetScaler can process traffic in several ways, for example Layer 2 mode, Layer 3 mode and as a full (reverse) proxy, and before you go and implement there are several considerations you need to take on how you would like to get the traffic processed, some of them include: Does the NetScaler need to be transparent in my networks?
Citrix just released a security advisory article regarding the SSL “poodle” vulnerability and how we can disable SSL 3.0 protocol on the Netscaler -> http://support.citrix.com/article/ctx200238 The article shows how we can disable SSL on vServers and on NSIP, MIP and SNIPs.