Personally I would like a knob to fix it to my liking, but I also would like it to auto log me out if there was no computer activity (not the ccmadmin but computer activity). Kind of like Office Communicator says inactive when you have not used it your computer for 5 minutes. then after 10 minutes it's away. a system where no computer activity would equal log off rather then no activity on the ccmadmin page equally log off. I may be neck deep in setting up services or troubleshooting something and someone comes in and needs something else that takes 20+minutes.<div>
<br></div><div>just my 2 cents</div><div><br></div><div>Scott<br><br><div class="gmail_quote">On Mon, Jun 8, 2009 at 11:26 AM, Justin Shore <span dir="ltr"><<a href="mailto:justin@justinshore.com">justin@justinshore.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">Bill Simon wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sounds to me like two measures are needed.<br>
<br>
One, a configurable timeout value.<br>
</blockquote>
<br></div>
Agreed. If a value is defined then it should be user-configurable after the fact too.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Two, some javascript that detects activity on a page such as clicking in and typing in form fields, for lengthy configuration sessions.<br>
</blockquote>
<br></div>
Now this would be a cool feature. The timeout is already JS driven. Sensing screen input and non-page-changing activity would be helpful. Still it doesn't help in the cases where I switch over to <a href="http://cisco.com" target="_blank">cisco.com</a> or a dead tree reference to figure out how to do something. Or answer a short call that ends up lasting 30m. Auto-logging out in such a short time is just not helpful.<br>
<br>
That said, if they would code in a way to keep track of your exact place including text box and menu values (even if they weren't yet submitted) as work in progress, then that would more or less solve the problem. I've seen several web GUIs do things like that.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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.<br>
</blockquote>
<br></div>
In a case like that then the policy on the workstation should lock the PC. It shouldn't be up to the apps themselves to kick the user off. The workstation policy should secure the PC for us, thus securing access to the individual apps. How would you feel if for security reasons your mail admins forced Outlook and all it's windows to auto-close after 20 or even 30m of no activity, losing everything you were working on in the mean time. I wouldn't like it....<br>
<font color="#888888">
<br>
Justin</font><div><div></div><div class="h5"><br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div></div></blockquote></div><br></div>