RE: FW: NoCatAuth Renewal isn't quite right.

Thanks for that Steve,

It turns out I did something really stupid (again) and when customizing the
renewal window I managed to delete the RenewalForm as well as the LogoutForm
which meant that the javascript never executed.

It's interesting to note that Meta Refresh works the first time but NoCat
relies on the Javascript for subsequent renewals, while I don't see any
problems with that (aside from the fact that some people may have javascript
disabled) it may help others that are troubleshooting the renewal process.

Matt

-----Original Message-----
From: Steve Platt [mailto:[email protected]] 
Sent: Tuesday, 5 July 2005 10:30 p.m.
To: Matt Courtney - PC Tronix
Cc: 'Schuyler Erle'; [email protected]; [email protected]
Subject: Re: FW: [NoCat] NoCatAuth Renewal isn't quite right. 


I am a little confused about how our own NoCatAuth setup is working too!
 ;-)

I'm no longer confident that the renewal process is working properly; some 
users are finding that they keep getting re-captured. One or two are even 
reporting that web pages they browse to (in Firefox) are being displayed IN 
THE LOGIN WINDOW! If that happens I am not surprised if they get
disconnected 
... but why does it happen?

I am also confused about the IdleTimout option, which seems to be set to 300

seconds - how does this interact with the LoginTimeout option?


I have LoginTimeout set to 600 and find that renewals are happening every
450 
seconds, as advertised in the login window.  However, is an IdleTimeout of
300 
sensible under these circumstances?

Also, in the status page, users often show up with negative values for 
"minutes left" - does that mean they have timed out already?

Anyway, I'll try to answer your question about the pop-up window script.

To start with the login window contains :-

 <meta http-equiv="Refresh" content="450;
URL=https://.../cgi-bin/login?pass=..
.

Later, I find the window source contains :-

 <meta http-equiv="Refresh" content="5; URL=http://...:5280/?ticket=...

All other references to "450" in the HTML look the same to me, it's just
this 
Content= bit that's changed. I don't know if this helps you Matt?

Is it stupid to have an IdleTimeout that's less than the loginTimeout?
Steve