1 of 1 people found this helpful
--> Like! <--
I am wondering: 1) how often this occurs for users, 2) what should be the optimal number "warning number of minutes" before session times out. I find this a very useful feature when I am in a banking application or in applications doing tasks that take a while and so there is a liklihood that you would be interrupted mid-stream.
Anybody else want to weigh in on the issue?
P.S. As for the configurable 30 minutes inactivity session timeout that is a general security issue and needs to be consistent across all tenants in a multi-tenant environment.
I searched Connect.Ariba.com and was surprised not to find an ER submitted. So today I submitted ER 1-BP05OB to address both the length of inactivity allowed as well as the visibility of the logout warning. Customers of OnDemand who require such a 30-minute restriction should perhaps pay for their own environment (shared with any others who have similar restrictions) rather than penalize all customers with this overly-restrictive inactivity logout. Additionally, for more complete mindshare, Ariba should want its users to 'log in and stay in' unless a security requirement within their company requires otherwise.