It sure seems like the license isn't being cached on disk (i.e. attached to the player instance & persisting on the client).
The symptom of the license "going away" and needing to be re-acquired - when the video player window (not the entire browser) exits - seems to support this.
We just have to figure out if it's content-related or client-related.
It looks like the license.caching=0 setting might be how the content is created. 0 means "don't write .LIC (license file) to disk" - which means it needs to re-acquire after you close the video player instance.
This setting value (0) specifically won't persist the license on the clients' disk.
The symptoms sound correct for this to occur.
Locally, you can check the /APSPrivateData2/... directory structure. If you are playing the video (after license acquisition) and no .LIC file appears underneath here, then the license is not being "cached' to disk and our educated guess is correct.
Ask the content provider if they are doing this and what they can do to better support your "public PC" type of infrastructure to persist licenses.
Just a complement.
policy.licenseCaching.duration=0 means disabling license caching on the disk. If content published with the setting, license will be cached in the memory.
Thanks Stephen and Hiroshi. I still don't understand though - this same piece of content when used on just about any other system does persist on disk. So if the "don't write to disk" parameter is part of the license definition, why does it only affect those using public computers (without access to the local disk)?
The behavior you are describing for the lab users sounds like a Private Browsing session. The question then is, why is the license flushed from memory at a different time in your tests with Private Browsing. There are a couple factors which might account for this difference:
- Are you and the lab users using the same browser and OS? Can you share the details?
- In Private Browsing mode, the licenses will not be written to disk and will only remain in memory while the Flash Player process is running. The Flash Player process will terminate when there is no Flash content playing in any browser window. Is it possible in your tests that there was another browser window aside from your player which was showing Flash content?