[cisco-voip] CCM 6.1 CCMAdmin timeout
Bill Simon
bills at psu.edu
Mon Jun 8 13:49:24 EDT 2009
Sounds to me like two measures are needed.
One, a configurable timeout value.
Two, some javascript that detects activity on a page such as clicking in
and typing in form fields, for lengthy configuration sessions.
I'd still like the "user walked away from terminal for lunch" security
of, say, 30 minutes time out, or even the 20 minutes it is now, as long
as the system can understand when there is non-GET/POST activity going
on on a page and not interrupt a configuration session.
Walt Moody wrote:
> Yes, Bill, I do (see this as a big deal). Whose security policy is
> this? Why would it be a hard and fast "rule" that every admin console
> time out after a fixed period of inactivity without regard to other
> tasks on other systems that may be required in order to complete the
> work? Why would technicians in a physically secure administration
> facility have to log on more than once per shift?
>
> You may not see the big deal about logging back in after a timeout, but
> others do. Why not have a default timeout enabled in the CUCM (and CER
> for that matter) with the institution having the ability to modify or
> disable it in accord with local security practices?
>
> Having a timeout is a good thing. Having it hard coded is not.
>
> -walt
More information about the cisco-voip
mailing list