Fri, 10 Apr 2026 18:27:17 +0000 https://bugs.horde.org/ticket/10433 Successful password change leads to infinite loading of site After successful password change any action in Horde makes the browser infinitly try to load the page. Even logout results in this behavior. The same with a page reload or manually entering the url. Only after completly closing the browser and reopening it shows the login screen again. Using the new password I can log in again. No possibility to reset credentials in applications is provided by the Horde Framework (Enhancement #10228), so as a workaround passwd needs to log out the user at the moment. Wed, 17 Aug 2011 09:08:20 +0000 https://bugs.horde.org/ticket/10433#t67003 > After successful password change any action in Horde makes the > browser infinitly try to load the page. Even logout results in this > behavior. The same > with a page reload or manually entering the url. > > Only after completly closing the browser and reopening it shows the > login screen again. Using the new password I can log in again. > > No possibility to reset credentials in applications is provided by > the Horde Framework (Enhancement #10228), so as a workaround passwd > needs to log out the user at the moment. > This doesn't happen for me with sql auth and ldap auth. Can you provide more Info? Which passwd backend are you using? (passwd/config/backends.local.php) Which Driver is used for Horde_Auth? (horde/config/conf.php) Wed, 17 Aug 2011 09:12:39 +0000 https://bugs.horde.org/ticket/10433#t67004 Request #10228. Wed, 17 Aug 2011 09:23:11 +0000 https://bugs.horde.org/ticket/10433#t67005 I tried to solve this with the help of Jan on the horde mailing list. I just have no idea how to correctly submit this patch. The information on http://www.horde.org/development/git#createcommit is not verbose enough for a git newbe. I did my best and hope it is alright. Please inform me what I can do better next time. Wed, 17 Aug 2011 09:28:36 +0000 https://bugs.horde.org/ticket/10433#t67006 This is no genuie duplicate since it provides a workaround until the "duplicated" bug is solved. If your policy sees this another way please merge the tickets if you like. Jan, your words on the horde mailing list on 27.07.2011 20:24 where: "Why don't you open a ticket and upload a patch? Thanks." So I did. Wed, 17 Aug 2011 09:36:23 +0000 https://bugs.horde.org/ticket/10433#t67007 > This is no genuie duplicate since it provides a workaround until the > "duplicated" bug is solved. If your policy sees this another way > please merge the tickets if you like. > > Jan, your words on the horde mailing list on 27.07.2011 20:24 where: > "Why don't you open a ticket and upload a patch? Thanks." > > So I did. Hi kareem, Not to offend you in any way but the diff file is empty. You should have mentioned it is about imp application auth. Other backends are working without problems so unconditional logout is no good option for these cases. What passwd backend is used here? Wed, 17 Aug 2011 09:57:38 +0000 https://bugs.horde.org/ticket/10433#t67009 > Not to offend you in any way but the diff file is empty. Whatever happened to the file I do not know, but I will try another upload. > You should have mentioned it is about imp application auth. Other > backends are working without problems so unconditional logout is no > good option for these cases. Ehm, no. It is about Horde auth using IMAP driver. I am not using imp directly as authenticator, although Horde may do that internally, which I do not know. My config regarding this is: horde4/config/conf.php: ... $conf['auth']['params']['hostspec'] = 'mail.hostname.de'; $conf['auth']['params']['port'] = 143; $conf['auth']['params']['secure'] = 'tls'; $conf['auth']['driver'] = 'imap'; ... horde4/imp/config/backends.php: ... $servers['imap'] = array( 'disabled' => false, 'name' => 'IMAP Server', 'hostspec' => 'mail.hostname.de', 'hordeauth' => false, 'protocol' => 'imap', 'port' => 143, 'secure' => 'tls', 'maildomain' => '', 'cache' => false, ); > > What passwd backend is used here? MySQL. I write to the same DB the IMAP-Server uses as authentication database. I have tried authenticating against the DB directly but regarding this problem there is no change in behaviour. Wed, 17 Aug 2011 11:59:09 +0000 https://bugs.horde.org/ticket/10433#t67010 >> Not to offend you in any way but the diff file is empty. > Whatever happened to the file I do not know, but I will try another upload. And again the file is empty after upload. Something is wrong here. I will try uploading a zipped version. Wed, 17 Aug 2011 12:02:36 +0000 https://bugs.horde.org/ticket/10433#t67011 >>> Not to offend you in any way but the diff file is empty. >> Whatever happened to the file I do not know, but I will try another upload. > And again the file is empty after upload. Something is wrong here. I > will try uploading a zipped version. And again. A zero byte file. This makes no sense. I will copy and paste the contents of the diff-file. ---------------------------- passwd/lib/Passwd.php ---------------------------- index 05612a8..71e612f 100644 @@ -105,6 +105,13 @@ class Passwd { { if ($GLOBALS['registry']->getAuthCredential('password') == $old_password) { $GLOBALS['registry']->setAuthCredential('password', $new_password); + + // Generate an authenticateFailure to force a logout after successful password change. + // This is a workaround until Horde Framework supports propagation of credential changes to applications + $GLOBALS['registry']->authenticateFailure('horde' , + new Horde_Auth_Exception( + 'Ihr Passwort wurde erfolgreich geändert. Bitte melden Sie sich neu an.', + Horde_Registry::PERMISSION_DENIED) ); } } Wed, 17 Aug 2011 12:04:57 +0000 https://bugs.horde.org/ticket/10433#t67012