My Oracle Support Banner

How to Verify if mod_osso Global Inactivity Timeout (GITO) is Working (Doc ID 357687.1)

Last updated on SEPTEMBER 01, 2017

Applies to:

Oracle Application Server Single Sign-On - Version 9.0.4.3 to 10.1.4.3 [Release 10gR1 to 10gR3]
Information in this document applies to any platform.
***Checked for relevance on 04-SEP-2014***

Goal

This note will describe a procedure to test whether or not the Single Sign-On (SSO) global inactivity timeout option is working properly for a mod_osso protected resource.

This note will only test the global inactivity timeout option and not the SSO session duration. The session duration, although closely related to global inactivity timeout, is slightly different. See note <> "What is the difference between the SSO session duration timeout and the global inactivity timeout values" for more information about the difference between the two timeouts.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 Overview of Configuration Steps
 Configure GITO timeout parameters
 Enable the HTTP Server to Check for Inactivity Timeouts
 Restart the iAS Components
 Test GITO
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.