a little, and most will roll on
tw
-Original Message-
From: CS [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 15, 2002 10:10 PM
To: CF-Talk
Subject: Re: Duplicate UserNames / Passwords logging
into a site
Another simple and efficient solution would be:
on database side, add
-Original Message-
From: CS [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 16, 2002 11:42 AM
To: CF-Talk
Subject: RE: Duplicate UserNames / Passwords logging into a site
I didn't give it much thought, you're right, session
management is the way to go.
Don Li
--- Tony Weeg [EMAIL
Another simple and efficient solution would be:
on database side, add a column like LogonYN (bit) (for
MS SQL Server) to the {user login} table, upon
successful login turn the flag to 1 (ON) -- the user
is login on now; when a user attempts to logon in,
verify this column as well, if it's 0 (this
: Re: Duplicate UserNames / Passwords logging into a site
Another simple and efficient solution would be:
on database side, add a column like LogonYN (bit) (for
MS SQL Server) to the {user login} table, upon
successful login turn the flag to 1 (ON) -- the user
is login on now; when a user attempts
: RE: Duplicate UserNames / Passwords logging into a site
what if user loses internet connectionthey are still logged
in to the site, and cant relogin now?
no
use session management and some client state management, set some
cookies and manage it that way.set the session timeout
Mark, I had this situation once where it was vital to lock out people in
this manner.
What I did was upon a successful login, I logged the date and time into the
user log, and the status of that user was changed to logged in. If
another user attempted to log in with that username/password
This might be a tricky one.
You can use an application variable that contains a list of all users on
the site. Perhaps you'll want to use a structure. Take the username as
the key and the date / time of there last access as the value. You'll have
to update this value on every page,
There are few options... Database/Application scope to store all the logged
in users and
check/authenticate every user aganist the scope. You would have to write a
routine
to clean up the application scope users.. as they log out.
Joe
-Original Message-
From: Mark Leder [mailto:[EMAIL
I don't think that there is clean way to accomplish this.
Because there is no good way to know when the user log off (for example if
the user closes the browser window, instead of clicking on the Deconnect
button...).
If you implement a system based on application scope (to register all the
Mark,
If you use session vars, simply set a session var with a value of UID:PWD.
Exampe: SESSION.Tracker = mark:12345
Then, upon login, validate against this. If you have a session var that has
the value mark:12345, then kick them out to a message that tells them that
the user is already
, October 14, 2002 1:59 PM
To: CF-Talk
Subject: RE: Duplicate UserNames / Passwords logging into a site
I don't think that there is clean way to accomplish this.
Because there is no good way to know when the user log off (for example if
the user closes the browser window, instead of clicking
Thanks everyone for taking time to respond.
GREAT ideas all. This really helps a lot in getting started.
Thanks,
Mark
-Original Message-
From: Matt Robertson [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 14, 2002 3:31 PM
To: CF-Talk
Subject: Duplicate UserNames / Passwords
12 matches
Mail list logo
