Session Logout problem with Templates

[vinny]

Hello,

I have assigned a Template for a particular Group. This Group has access to THEIR OWN assigned Downloads, etc. When the User logs in, the Template shows fine and their Downloads show fine. However...

...when User Logs Out -- the Template retains the session and I can tell this because the Title remains on the page and I can still see their Downloads folder.

I'm not sure if this is a new or old problem, I just bought v3.04.10 and this is the first security issue I've encountered thus far. I've tested this in Firefox but no other browser yet, fyi....

Any help? TIA

[vinny]

Anyone else not having Logout delete Cookie Sessions?

[Astrix_jpl]

Yes, we have the same problem. Don't know how to fix it - anyone?

[Astrix_jpl]

Does this problem have anything to do with this setting in the config.shared.php file in the admin directory?

PHP Code:
// Change this if you experience login loops
//ini_set('session.use_cookies',false);

By the way, our Kayako SupportSuite is hosted - how can I then, if possible, access this php file?

[meltemi]

I don´t know if this is a solution for your problem. We had a problem that during the logout process always the default template was choosen by the system. This workaround was helpful for us. (But it only works with the non-hosted version):

1. change the template "general -> navbar" and replace the logout-link with a formular:

<form name="logoutform" action="<{$basepath}>" method="POST">
<input type="submit" name="logoutbutton" value="<{$language[logout]}>" class="loginform_go">
<input type="hidden" name="_m" value="core">
<input type="hidden" name="_a" value="logout">
<input type="hidden" name="group" value="your_preferred_template">
</form>

2. open the file " ../modules/core/client_loginhandler.php" and change in the logout-part as presented below:

printRedirect($_SWIFT["language"]["loggingout"], "index.php?logoutresult=".urlencode($logoutresult)."&group=".$_POST["group"], true);

Have a nice day!

[vinny]

The newest build has changed the fix for me, thanks Kayako

[rrnworks]

Are you using hosted or non-hosted? The 3.10.02 "stable" release of non-hosted does not seem to fix this problem.

[mopa]

Since I have been very interestered in this one - I will just inform that this issue have been solved in the 3.11.00 version.