Session timeout for OWA 2010

You can now force OWA 2010 connections to time out after a specified period of inactivity. OWA sends repeated keepalive requests to the server to prevent timeouts. Keeping the connections open can interfere with single sign-on.

To force OWA 2010 to timeout after a specified period by using the command line interface

At the command prompt, type the following commands:

  • add tm trafficAction <actname> [-forcedTimeout <forcedTimeout> -forcedTimeoutVal <mins>]

    For <actname>, substitute a name for your traffic policy. For <mins>, substitute the number of minutes after which to initiate a forced timeout. For <forcedTimeout>, substitute one of the following values:

    • START—Starts the timer for forced timeout if a timer has not already been started. If a running timer exists, has no effect.
    • STOP—Stops a running timer. If no running timer is found, has no effect.
    • RESET—Restarts a running timer. If no running timer is found, starts a timer just as if the START option had been used.
  • add tm trafficPolicy <polname> <rule> <actname>

    For <polname>, substitute a name for your traffic policy. For <rule>, substitute a rule in NetScaler appliance default syntax.

  • bind lb vserver <vservername> –policyName <name> -priority <number>

    For <vservername>, substitute the name of the AAA traffic management virtual server. For <priority>, substitute an integer that designates the policy’s priority.

Example

add tm trafficAction act-owa2010timeout -forcedTimeout RESET -forcedTimeoutVal 10
add tm trafficPolicy pol-owa2010timeout true act-owa2010timeout
bind lb vserver vs-owa2010 -policyName pol-owa2010timeout -priority 10

Session timeout for OWA 2010