I do the same thing but check for it in the menu which is a presentation file. If it is empty I redirect to logout.taf which purges all user scope
Dan variables. -- Dan Stein Digital Software Solutions 799 Evergreen Circle Telford PA 18969 Land: 215-799-0192 Mobile: 610-256-2843 Fax 413-410-9682 FMP, WiTango, EDI,SQL 2000 [EMAIL PROTECTED] www.dss-db.com > From: "Atrix Wolfe" <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > Date: Tue, 14 Jan 2003 15:43:18 -0800 > To: Multiple recipients of list witango-talk <[EMAIL PROTECTED]> > Subject: Re: Re: Re: Witango-Talk: user timeout > > well how we check when a user times out is pretty simple... > > first off you need a user var that is set as soon as the user is "logged > in", this could be something like... user$username or user$userid or > anything like that. > > Im not sure how you do it, but we have a menu and when someone selects > something from the menu it redirects them to a different .taf file depending > on their selection. > > Inside of these .taf files at the top it checks "if username is empty, > redirect to login page". This has 2 benefits. The first being when a user > times out, username becomes empty and they get sent to the login page next > time they try to do anything. Secondly, if someone were to try to break > past the login page by putting something like this in their browser: > www.yourserver.com/admin.taf, their username would be empty so they would > get redirected to the login screen. > > hope this helps > Atrix > > ----- Original Message ----- > From: "Wilcox, Jamileh" <[EMAIL PROTECTED]> > To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]> > Sent: Tuesday, January 14, 2003 2:48 PM > Subject: RE: Re: Re: Witango-Talk: user timeout > > > What Tango error are you getting? > > The problem I'm having is that they log out and come right back in. > They should get a login page with no menu, but they don't - they get the > page with menu as if they'd logged in. Then when they fill out the > form, they get a db error because their userID variable is empty. I > hadn't coded a check for the user variables, because I didn't think > they'd be able to get to the forms without logging in first. > > Question - how are you checking for the user timeout? I'd like to do > that, but I haven't figured out how in Tango2000 (which is the same as > Tango 4, right?) > > >> -----Original Message----- >> From: Atrix Wolfe [mailto:[EMAIL PROTECTED]] >> Sent: Tuesday, January 14, 2003 1:57 AM >> To: Multiple recipients of list witango-talk >> Subject: Re: Re: Witango-Talk: user timeout >> >> >> you know thats what im thinking too. >> >> the problem im experiencing is they log in, time out, and >> when they try to access part of a taf after they have timed >> out it redirects them to the login screen. They re-login and >> then right about there itll throw a tango error. >> >> This is one of those problems that seems to be at the low end >> of the priority list but ill do some more research and maybe >> ill find some useful info and we can find the root of this >> problem whether it be in our code or in the engine itself. >> >> ----- Original Message ----- >> From: "Wilcox, Jamileh" <[EMAIL PROTECTED]> >> To: "Multiple recipients of list witango-talk" >> <[EMAIL PROTECTED]> >> Sent: Monday, January 13, 2003 1:37 PM >> Subject: RE: Re: Witango-Talk: user timeout >> >> >> Atrix - I didn't quite follow what's happening. When are >> your users getting errors (e.g., on the login or later) and >> what errors are they getting? >> >> I've been having some problems where users log out & >> immediately hit the application again. There seem to be some >> variables that aren't necessarily reset as part of the USER >> scope - maybe some sort of session state or session cookie. >> >> jamileh >> >>> -----Original Message----- >>> From: Atrix Wolfe [mailto:[EMAIL PROTECTED]] >>> Sent: Saturday, January 11, 2003 3:27 AM >>> To: Multiple recipients of list witango-talk >>> Subject: Re: Witango-Talk: user timeout >>> >>> >>> i had this in origionaly but it disapeared mysteriously: >>> >>> im in windows using tango server 4. something (not sure how to tell >>> version # on server) but editor is 4.05.043 and it came as >> part of an >>> r:tango release if that helps w/ understanding what version >> im using. >>> >>> ----- Original Message ----- >>> From: "Atrix Wolfe" <[EMAIL PROTECTED]> >>> To: "Multiple recipients of list witango-talk" >>> <[EMAIL PROTECTED]> >>> Sent: Saturday, January 11, 2003 1:21 AM >>> Subject: Witango-Talk: user timeout >>> >>> >>>> hello, i was wondering what happens when a user times out >>> exactly. I >>>> was under the assumption that all the user$ vars for that >> user were >>>> wiped out completely and so basicly they were a "fresh >>> user" if they >>>> tried to access things (<@arg>'s of course still part of >> forms and >>>> all). >>>> >>>> The reason im asking is because we have a system where >> when a user >>>> times >>> out >>>> it redirects them back to the login screen, but we have had some >>>> issues >>> with >>>> users who have timed out then re-logged in and caused >>> errors where a >>>> user who just logged in for the first time does not have >>> errors. We >>>> dont use >>> any >>>> domain scope variables so that isnt the problem. It >> would be a big >>> stretch >>>> to say it was caused by <@arg>'s since the login page >>> doesnt rely on >>>> or >>> use >>>> any <@arg> arguments. >>>> >>>> Anyone have any idea on this? >>>> >>>> PS i dont have to put money in the jar since its actualy >>> called "Tango >>>> editor" right? (: >>>> >>>> >>> >> ______________________________________________________________________ >>>> __ >>>> 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 >>> >> ______________________________________________________________ >> __________ >> 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 >> > ________________________________________________________________________ > 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 > ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
