LDN - Luminis Developer Network

Our Luminis implementation has been largely successful. We've got the data to show that people are using it. They routinely give us positive feedback for a few of our more popular channels that have made their lives easier (yay us!) and they will tell us pretty darn quickly if they find a typo (boo us!) However, the one piece of feedback we get most often is not positive. Our users are dreadfully unhappy with the default system timeout (currently set to 22 minutes to coordinate the pass-through authentication with our shortest external system timeout.) We are dreaming about a "keep me logged in" button or a "public maching/private machine" option that would toggle the session timeout to a much longer timeout when selected. But, our crack developer left the company so this project is on hold.

My colleague and I have been looking at enabling the user-specific timeout that is provided with the out-of-the-box Luminis product. If we can create a reasonable timeout range and allow our users to set this themselves with a hearty warning about doing so on public machines, then perhaps this will satisfy the users need. However, I can't find anything in the documentation on HOW the users would set this property. We can enable that configuration, set the range and the minimum timeout, but what is the method that individuals will use to change their timeout?

Is anyone using user-specific timeout out there? Or just know what the mechanism is?

Thanks for any help you can provide.

Tracy Axelson
Clark University