Re: Login Security

Another thing you can do is only allow each user to maintain one
session. Keep a record of the session hash key in the database and
compare on each request. If a user logs in from a different machine
they will get a new session hash and invalidate the old session hash.
This gets around the lockout situtations you could run into.

-Mark

On Mar 26, 2:00 pm, "Dave Maharaj :: WidePixels.com"
<d...@widepixels.com> wrote:
> Just a general question.
>
> Can I restrict a user to only allow the user to be logged in from one
> location...sounds stupid but some people share acct info with friends /
> family so this would restrict a user from logging in only once.
>
> So for example on login update a field in the user table LOGGEDIN to 1 and
> on logout set it to 0. So if Jeff shares his acct info with his wife and
> Jeff logs in then his wife tries to log in (it checks LOGGEDIN if set to 1
> someone is already logged in on that acct) she cant because Jeff is already
> logged in.
>
> Or does cake take care of this? If so are both allowed to login in at the
> same time? Does 1 get the boot?
>
> Dave
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to cake-php+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---