Forum Discussion
I am seeing the persistence entries via tmsh. I'd paste the output but the TICKET is in the neighborhood of 200 characters long and reads as a single line on the CLI output.
This is a Citrix-like app, a user logs in via real HTTPS to a web interface which presents a desktop. The app server that actually runs the apps that are presented then open a session to the web interface as well, which is connected, by TICKET, to the user session and RDP is essentially tuneled back via SSL. (A least that is how it has been explained to me.) The web interfaces don't keep any state between themselves, so having the app server land on a different web interface is bad. The vendor claims the only way to do persistence is based on the TICKET id in the payload.
Hopefully that maybe clears up a bit. Everything seems to be working, except for getting everyone pinned to the same web interface.