Application Goes Unresponsive after Reaching Max-timeout

book

Article ID: 197370

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On Agents (SiteMinder) SITEMINDER CA Single Sign On Federation (SiteMinder)

Issue/Introduction

Once user session reaches the max timeout defined in the partnership, the application becomes unresponsive, and none of the onscreen buttons work. The only way out of this seems to be refreshing the URL, which takes the user through ADFS login.

Cause

Application logic is driving this behavior since the web agent responds exactly the same way whether max or idle timeout is reached.  The application in question is handling idle timeouts as expected and only showing the problem with max timeout.  It also doesn't matter whether the user obtained the session via a configured Siteminder authentication scheme or a federation partnership: max and idle timeout settings are set during authentication, regardless of the authentication method.

Environment

Release : 12.8

Component : SITEMINDER -POLICY SERVER

Resolution

Application logic is driving this behavior as Siteminder will take the same action for idle timeout as it will for max timeout being reached.  Examine and fix the application logic.