Hi Paul,
Off the top of my head, it sounds like the user's browser still has the
'sesssion-cookie' still loaded after you <@PURGE SCOPE=USER>?
The 'session-cookie' is assigned automatically by Witango when you first
open a TAF.
You might want to try either controlling your local$httpHeader output
for all TAFs to not assign the 'session-cookie' (which means all your
TAF links have to use <@USERREFERENCEARGUMENT>) or specifically try and
overwrite the cookie value at the time of your <@PURGE>.
The 'session-cookie' is called 'Tango_UserReference'.
Hope this helps. Cheers....
>>> [EMAIL PROTECTED] 07/15/02 08:35 AM >>>
I use NT Authentication to validate users logging in to my site. I
provide
a logout button which will purge the user variables upon exit. If the
user
does not close his browser application and goes back to my site, the
program
is still able to pull his userid from some session variable and let him
back
in. Is there a variable that can be cleared during the logout process
that
will force the user to authenticate again even when they don't close
their
browser.
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
