Forum Discussion
Hi, guys...
Just some thoughts here...
This is definitely possible, with some caveats. There's logic that can be used to achieve what you're trying to do using our Dynamic Session Detection/username persistence solution for your internal users. Right now, it's iRules "but" we'll be releasing a beta iApp very soon via DevCentral that will help automate the entire setup.
For internal users, we can use this iApp/Username persistence, as it already has logic to route internal users by AD group.
The external side is where it gets trickier because of the RSA integration. The username persistence iRule/beta iApp will not support RSA, since there's an extra layer of authentication to deal with. Additionally, some folks use different ID's for RSA than Active Directory - which makes locating users a more challenging.
How many users access your View environment externally vs. internally?
Justin
- JSinclair_21981Sep 08, 2015NimbostratusJustin, Thanks for the reply. That does sound like a viable solution. Right now all of our users connect both internally and externally (roughly 400). While there are many that have a zero client at their desk, we may give them the option of connecting from home using an RSA token. When a user connects internally, will their PCoIP traffic bypass F5 and communicate between the client and desktop? I have been tossing around the idea of upgrading our 5.3 setup to 6.2 and look into Cloud Pod Architecture. Not sure if this will help, and I'm not exactly comfortable upgrading our production environment unless it's necessary. I would be interested in testing out the iApp when it's released. Do you have any ETA? Thanks! Jason