Cookie Persistence Issue with Default Setting in LTM V10

The direction I've been going with this is to determine if you're using session-based cookies. It's a pretty common problem with APM when a browser initiates an external process and that process can't pass through the same authenticated policy. The most prominent reason for this is that the external process cannot use the session cookies that are in the browser's memory space. When you enable the session expiration option in the cookie persistence profile, you're telling LTM to set a session cookie, one that has no expiration and that will live in browser memory only. If you uncheck that value, and optionally enter date/time values below it, it'll create a file-based cookie, one that is probably accessible to the external process. If you look at client side captures, you'll most likely see that the Set-Cookie header coming from the LTM has an "expires" tag.