Wednesday, September 4, 2013
Session timeout as the name describes, is the time period after which the session object of a web application expires. The timeout period can be a fixed period (Hard Timeout) or, an inactivity period (soft timeout) when user does not refresh or request a page. Once the session has reached the timeout, user is required to re-authenticate to access the web application. Hard Session timeout is a defined timeout period of the session ID irrespective of user activity. If the application has a hard session timeout of say 9 hrs, the user will be asked to re-authenticate after 9 hrs even if the session was used actively.
Hard and Soft session timeout configuration is a security control measure. They protect the user session from security attacks like CSRF, session fixation etc.
There are few ways to configure hard and soft session timeout for applications. We will discuss mainly the soft session timeout configuration for Oracle Identity Manager (OIM) version 11gR2PS1.
If an application is protected by an Access Management solution, then the application session timeout must be configured through the Access Management tier.
For a standalone application (not using Single Sign On), the (inactivity) session timeout configuration can be done through the application deployment descriptor files (web.xml, weblogic.xml (in case application is deployed in Weblogic Application Server)) or it can be configured using weblogic deployment plan.
In this post we will discuss the session timeout configuration for OIM Web Applications using weblogic deployment plan.