Could you please explain what you did to store the session info in the
database? I am trying to set up something just like that.
Thanks
On 5/29/06, Dave <[EMAIL PROTECTED]> wrote:
>
> What I ended up doing was creating my own database-driven solution.
> Turns out to be pretty simple. You don't ne
Hi! you can work with cookies + encryption with this
http://rossoft.wordpress.com/2006/05/22/cookie-component/
I suggest you to save in the cookie the user+password all encrypted in
reversible way. The user can't modify the content because he doesn't
know the key for encrypt.
--~--~-~-
Hi Dave,
I wondered if someone more knowledgable would chip in on this thread:
Glad you found a solution. I suggested DB sessions primarily because it
would be easier to debug and find out what was happening should things
go wrong (and having never expiring sessions is a situation that may
well
What I ended up doing was creating my own database-driven solution.
Turns out to be pretty simple. You don't need encryption since all you
have to store on the client is a key. So, I just used md5 hashing to
create a key in a cookie, and added a table and model for the session
information. Authent
How would the Cake database sessions help? Wouldn't there still be a
browser component (cookie, URL key) that would go away at the end of
the browser session?
Otherwise, I'll try what you suggested. The encryption class you
supplied looks like just the thing. Do you know how to make sure all
acti
Hi Dave,
Sessions don't last longer than the window is open*.You might want to
look into useing Cake database sessions.
If you use 2 way encryption you can store something in a cookie which
is neither the users password, nore their DB stored password and still
authenticate who they are.
http://r
Are you saying there's no way for a session to persist across browsers
launches? If so, then a cookie may be the only way.
I was using a cookie for a while but having issues. For one thing, at
least in Camino I was getting different cookies set for different
controller paths; for another, I'm usi
What have you got session.cookie_lifetime , session.gc_maxlifetime (and
any others that are useful) set to in your ini file?
I don't know your app of course, but maybe using a "remember me" cookie
and recording anything else the user might want to access from hour to
hour in a cookie would avoid
Hmm...this doesn't seem to help. I've set CAKE_SESSION_TIMEOUT to a
ridiculously high number (604800) and just in case set CAKE_SECURITY to
'low'. The session still times out after a couple hours and I have to
log in again.
--~--~-~--~~~---~--~~
You received this
In app/config/core.php on line 108:
/**
* Set Cake Session time out.
* If CAKE_SECURITY define is set
* high: multiplied by 10
* medium: is multiplied by 100
* low is: multiplied by 300
*
* Number below is seconds.
*/
define('CAKE_SESSION_TIMEOUT', '120');
Hope that helps,
Adam
--~--
I'm using the Cake Session component to store user login information.
This is a Web app for which the user will want to remain logged in
indefinitely. Right now, after a little while the session information
appears to be gone (and thus the user is no longer logged in). How can
I change this?
--~
11 matches
Mail list logo
