Hi Ben,

I have a site with members access only. Members login at another ‘co-site’.
Entering the part of the site driven by EE I provide logmein with username from the ‘co-site’.
Both sites have the same usernames. I disabled the anonymous login. When using ‘User Session Type’ with ‘cookies and session-id’ all works fine. I cannot use ‘session_id’ as it conflicts the ‘co-site’.
However when setting ‘User Session Type’ to only ‘cookies’ my members of the EE driven site are automatically logged-in after closing the browser, even the next day. It’s not safe.
I guess this is something in the twilight of logmein and EE but I need a direction where to look. Has EE or logmein the ‘remember me’ option activated and how can I disable that?
Or is it possible to change the setting of logmein so that users are always logged out after, say, two hours of inactivity.

This topic is hot for me now. Any suggestions?

ron00nor - 18 May 2009 03:21 PM

This topic is hot for me now. Any suggestions?

you can set the expiration time to whatever you want:

The expire parameter is optional and sets the expiration time in seconds of the cookie. So in the example above the user will be logged in for only 5 minutes. The default value is 1 day.

Hi Ben,

The expire parameter is set to 43200.

but seems to do nothing because when the user closes his browser, then the next day the user is automatically logged in.
Do you know if EE has a general setting for automatic login?

UPDATE 2009-05-23:
I did a bit of testing and this showed that logmein is working perfect as it should. Something else is messing up.

CimexMedia - 18 December 2008 08:17 AM

Has anybody encountered problem with browsers other than Firefox ?

In Firefox, when I use {exp:logmein:now username=“website_user” expire=“300”}

I get the following cookies :

exp_anon          
exp_userhash    
exp_uniqueid    
exp_expiration

But I don’t with Opera, Safari, IE, etc… And therefore, my SAEF submission fails with : “You must be a logged-in member of this site in order to perform this action”

Has anyone encountered this before ?

Thanks

—EDIT—

Sorted, it had nothing to do with the plugin but the webserver time was off and the cookies were sent to the browser with a stale expiry date (oddly Firefox didn’t mind…)

I should note, I had this exact same problem but I was able to fix the issue by setting the Optional Cookie Domain setting located at

CP Home ›  Admin ›  System Preferences ›  Cookie Settings

hope this helps anyone else with this problem

strange why fireox has no issues. and apologies for the thread necro

such a great idea, looking forward for that..