[Tickets #11766] Re: [passwd] imp is not activated.

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/11766
------------------------------------------------------------------------------
  Ticket             | 11766
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | [passwd] imp is not activated.
  Queue              | Passwd
  Version            | Git develop
  Type               | Bug
-State              | Assigned
+State              | Resolved
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Ralf Lang (B1 Systems GmbH), Horde Developers
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2013-03-12 17:05) wrote:

After mulling this over, the only safe and reasonable solution is to  
destroy the Horde session if the password change would affect anything  
within the session.  This is because, even with registry calls, there  
can be no guarantee that, for example, an admin hasn't cached  
something relating to the old password in a hook.

Our backend is not optimized to handle this kind of invasive session  
change.  Nor should it.  This is an acceptable solution (and the  
solution the vast majority of applications use).