For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Justin_Venezia_'s avatar
Justin_Venezia_
Icon for Cirrus rankCirrus
Sep 08, 2015

Internally, yes - the connection is handed off and will not pass through the BIG-IP.

 

For external users, you may want to consider pass/proxying the traffic using the APM PCoIP Proxy, since we can then use some simple logic to route users to the right View Pod based on AD membership.

 

If you choose to do this through Security Server with RSA, we can't do anything (as I mention above).

 

Regarding Cloud Pod - not sure if this will help, since you have to merge pools together through the use of global entitlements. Also, you will need to upgrade your legacy environment.

 

Regarding the iApp, I am waiting to test one item and then we'll release to BETA on DevCentral. Hoping to have that wrapped up this week (fingers crossed)...

 

Justin

 

JSinclair_21981's avatar
JSinclair_21981
Icon for Nimbostratus rankNimbostratus
Sep 08, 2015
Makes sense. As for the RSA piece, why couldn't I just setup a separate iApp using the current load-balancing APM? The external IP will resolve differently anyway. I was able to get APM to select the appropriate View Connection Server based on AD groups, it just proxied everything through it, which I don't want for Internal. For external, I would definitely want that. The beta iapp could be setup for Internal only.