[Tickets #9733] Re: Password lost during hordeauth authentication via API

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/9733
------------------------------------------------------------------------------
  Ticket             | 9733
  Updated By         | arjen+horde at de-korte.org
  Summary            | Password lost during hordeauth authentication via API
  Queue              | Horde Base
  Version            | Git master
  Type               | Bug
  State              | Resolved
  Priority           | 2. Medium
  Milestone          | 4.1
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


arjen+horde at de-korte.org (2012-09-29 09:58) wrote:

> This should be good now. Includes the following commits:
>
> http://lists.horde.org/archives/commits/2012-September/016282.html
>
>
> If you could test these on your setup before they are released, that  
> would be a big help.

With all these patches applied, there is one thing left. I use  
memcache as a session handler (config/conf.php):

$conf['sessionhandler']['params']['track_lifetime'] = 43200;
$conf['sessionhandler']['params']['track'] = true;
$conf['sessionhandler']['type'] = 'Memcache';
$conf['sessionhandler']['memcache'] = false;

ActiveSync now no longer creates (or leaves behind abandoned)  
sessions, however I see zero length sessions popping up under the  
'session.path' as defined in 'php.ini':

session.save_handler = files
session.save_path = "/var/lib/php5"

These empty sessions are created when ActiveSync is run. I never  
noticed these empty sessions before, so I tried if adding

$session->setup(false, $args['session_cache_limiter']);

that was commented out for a while (and now removed) in Registry.php  
made a difference. It did, no more zero length sessions are created.  
Could it be that above line is actually doing something useful?