[sork] Horde hangs after changing password (passwd 4.0.0alpha1)

[Felipe Scarel]

So, any follow-ups on this issue?

On Tue, Oct 18, 2011 at 10:58, Felipe Scarel <fbscarel at gmail.com> wrote:

> I applied the patch on
> http://git.horde.org/horde-git/-/commit/60c7d1fe1d8338c512cf02ceeb2bcd61b8e8e44e#diff-1 ,
> with no luck so far.
>
> What happens is the following:
>  * User accesses the Passwd screen;
>  * User types old password and two matching new passwords;
>  * Horde/IMP correctly changes the password in the LDAP database (in my
> case, I'm using a hook script to do so);
>  * Page refreshes and the notification "Password changed on LOCATION." is
> shown;
>  * The sidebar does not get loaded anymore, and all the menu elements from
> the upper menu (on Traditional mode) disappear, aside from "Password",
> "Problem", "Help" and "Log Out". So, essentially, the only option left for
> the user is to either change his password again, or log out;
>  * If the user clicks "Log Out", the page enters an endless refresh loop;
>  * The only solution I've found so far is to erase browser cache, including
> cookies, and login again with the new, changed, password.
>
> Thanks a lot for your help Jan (and others from the ticket thread). If
> there's any further information I can provide, I'll be happy to do so.
>
> Regards,
> fbscarel
>
> On Tue, Oct 18, 2011 at 06:09, Jan Schneider <jan at horde.org> wrote:
>
>>
>> Zitat von Felipe Scarel <fbscarel at gmail.com>:
>>
>>
>>  Hello all,
>>>
>>> I recently installed the passwd plugin via PEAR (from pear.horde.org),
>>> version 4.0.0alpha1, the latest available. My Horde, IMP and other
>>> applications have also been recently updated.
>>>
>>> I'm using LDAP to store user information, and have setup a hook function
>>> to
>>> gather the user's DN from the database. So far, that setup works and I
>>> can
>>> change passwords without trouble.
>>>
>>> However, as soon as I successfully change passwords, the user seemingly
>>> gets
>>> "locked out" of Horde, i.e. the browser hangs up, as if Horde doesn't
>>> allow
>>> the user to access resources anymore with the old password. The only
>>>
>>
>> What do you mean with "locked out"? What happens if he tries to access
>> "resources" and what are those "resources" actually?
>>
>>
>>  solution is to delete the browser cookie and login again with the new
>>> password.
>>>
>>> Is there any solution to that problem? Any pointers are greatly
>>> appreciated.
>>>
>>
>> Could be http://bugs.horde.org/ticket/**10228<http://bugs.horde.org/ticket/10228>
>>
>> Jan.
>>
>> --
>> Do you need professional PHP or Horde consulting?
>> http://horde.org/consulting/
>>
>> --
>> Sork mailing list - Join the hunt: http://horde.org/bounties/#**sork<http://horde.org/bounties/#sork>
>> Frequently Asked Questions: http://horde.org/faq/
>> To unsubscribe, mail: sork-unsubscribe at lists.horde.**org<sork-unsubscribe at lists.horde.org>
>>
>
>