RE: URL refresh in passive mode
"Scott Tully" <[email protected]>
| Newsgroups | gmane.network.nocat |
|---|---|
| Organization | Public IP Services |
| Message-ID | <003b01c4a9c5$4544e150$6501a8c0@workstation1> |
Cool. Like I said I wrote my Authserver in java so I really had to figure out the NoCat magic. Very clever the way you guys made this work... Hats off. Scott ->-----Original Message----- ->From: Schuyler Erle [mailto:[email protected]] ->Sent: Saturday, October 02, 2004 9:01 AM ->To: Scott Tully ->Cc: 'Sameer Verma'; [email protected] ->Subject: Re: [NoCat] URL refresh in passive mode -> -> ->That's exactly right -- this is the best explication of ->"passive mode" I've seen. -> ->SDE -> ->* On 1-Oct-2004 at 8:48PM PDT, Scott Tully said: ->> ->> The popup only talks to the Authserver to re-authenticate the user. ->> The popup is really a way for the Authserver to bounce a ->http request ->> off the client machine to the gateway. It's the only way the ->> authserver can get the ticket to the gateway when it's nat'ed on a ->> LAN. (OK, not the only way, but it makes NoCat easy to distribute) ->> ->> The ticket contains user specific data like username, mac, ->and group ->> encrypted in a gpg encoded string. The ticket is how the ->gateway knows ->> to renew a specific user session. The session is renewed ->for another ->> 600 seconds or whatever the timeout is set to (450 insures that the ->> request is received in time). If the gateway doesn't receive the ->> ticket in 600 seconds, then the session expires and the ->user gets denied then ->> re-captured and directed back to the login... ->> ->> Or something like that..... ->> ->> Scott ->> ->> ->> _______________________________________________ ->> NoCat mailing list ->> [email protected] http://lists.nocat.net/mailman/listinfo/nocat -> -> ->