Tickets :: [#12538] Access Fails After Password Change with LDAP auth

6.0.0-alpha14

6/27/25

Summary	Access Fails After Password Change with LDAP auth
Queue	Passwd
Queue Version	5.0.0
Type	Bug
State	Resolved
Priority	2. Medium
Owners	slusarz (at) horde (dot) org
Requester	adorman (at) ironicdesign (dot) com
Created	08/06/2013 (4343 days ago)
Due
Updated	08/20/2013 (4329 days ago)
Assigned	08/06/2013 (4343 days ago)
Resolved	08/08/2013 (4341 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

08/20/2013 02:38:45 PM	cmartinez (at) scholem (dot) edu (dot) ar	Comment #9	Reply to this comment
[Show Quoted Text - 16 lines][Hide Quoted Text] It DOES fix the case where logout => true, although I would prefer the subsequent login to redirect to the portal page (/services/portal/), or whatever the default after login is, instead of /passwd. Fixed in Horde_Core 2.6.7. It unfortunately does not fix the case of logout => false. When I tested that setting I was not logged out, but the next feature I tried, the portal in my case, generated another auth error that required clearing the cookies before I could get back in. That's the entire point of the 'logout' parameter. You can't continue using Horde if the password you just changed is the authentication backend used to authenticate to Horde. Hello. I have the same problem. Where can I get the Horde_Core 2.6.7.?

08/08/2013 06:41:28 PM	Michael Slusarz	Comment #8	Reply to this comment
I agree you should be logged out. What I should have said is I wonder why the logout parameter is there in the first place if the only reasonable value is true. But perhaps that is a reasonable value for other settings of the authentication backend. There is no requirement that you need to change a password associated with Horde authentication. You can change passwords completely unrelated to any backend Horde is using.

08/08/2013 01:58:05 PM	adorman (at) ironicdesign (dot) com	Comment #7	Reply to this comment
Fixed in Horde_Core 2.6.7. And it works great, now it takes me back to a normal opening page. Thank you. It unfortunately does not fix the case of logout => false. When I tested that setting I was not logged out, but the next feature I tried, the portal in my case, generated another auth error that required clearing the cookies before I could get back in. That's the entire point of the 'logout' parameter. You can't continue using Horde if the password you just changed is the authentication backend used to authenticate to Horde. I agree you should be logged out. What I should have said is I wonder why the logout parameter is there in the first place if the only reasonable value is true. But perhaps that is a reasonable value for other settings of the authentication backend. In any case, I would suggest this particular ticket can be resolved and again, thank you.. Andy Dorman

08/08/2013 05:24:37 AM	Michael Slusarz	Comment #6 State ⇒ Resolved	Reply to this comment
It DOES fix the case where logout => true, although I would prefer the subsequent login to redirect to the portal page (/services/portal/), or whatever the default after login is, instead of /passwd. Fixed in Horde_Core 2.6.7. It unfortunately does not fix the case of logout => false. When I tested that setting I was not logged out, but the next feature I tried, the portal in my case, generated another auth error that required clearing the cookies before I could get back in. That's the entire point of the 'logout' parameter. You can't continue using Horde if the password you just changed is the authentication backend used to authenticate to Horde.

08/08/2013 05:22:41 AM	Git Commit	Comment #5	Reply to this comment
Changes have been made in Git (master): commit 0b7d2aba8ba95ae5e3c717c3ff11a464f652b6fa Author: Michael M Slusarz <slusarz@horde.org> Date: Wed Aug 7 23:19:07 2013 -0600 [mms] Don't redirect to current page's URL when logging out with a custom message (~~Bug #12538~~). framework/Core/lib/Horde/Registry.php \| 2 +- framework/Core/package.xml \| 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) http://git.horde.org/horde-git/-/commit/0b7d2aba8ba95ae5e3c717c3ff11a464f652b6fa

08/06/2013 11:32:28 PM	adorman (at) ironicdesign (dot) com	Comment #4	Reply to this comment
Does this fix? Michael, thank you. It DOES fix the case where logout => true, although I would prefer the subsequent login to redirect to the portal page (/services/portal/), or whatever the default after login is, instead of /passwd. It unfortunately does not fix the case of logout => false. When I tested that setting I was not logged out, but the next feature I tried, the portal in my case, generated another auth error that required clearing the cookies before I could get back in. But I think this is real close to a fix.

08/06/2013 10:59:49 PM	Michael Slusarz	Comment #3 State ⇒ Feedback Assigned to Michael Slusarz	Reply to this comment
Does this fix?

08/06/2013 10:59:22 PM	Git Commit	Comment #2	Reply to this comment
Changes have been made in Git (master): commit c68aef7033efb7b37f3d623eca66eb5692f8395e Author: Michael M Slusarz <slusarz@horde.org> Date: Tue Aug 6 16:58:50 2013 -0600 Possible fix for ~~Bug #12538~~ passwd/lib/Basic.php \| 6 ++++-- 1 files changed, 4 insertions(+), 2 deletions(-) http://git.horde.org/horde-git/-/commit/c68aef7033efb7b37f3d623eca66eb5692f8395e

08/06/2013 06:35:02 PM	adorman (at) ironicdesign (dot) com	Comment #1 State ⇒ Unconfirmed New Attachment: horde_passwd_ticket_doc.txt Patch ⇒ No Milestone ⇒ Queue ⇒ Passwd Summary ⇒ Access Fails After Password Change with LDAP auth Type ⇒ Bug Priority ⇒ 2. Medium	Reply to this comment
Horde 5.1.1, passwd 5.0.0: When using LDAP auth, I receive an authentication error after changing my password. With passwd/backends.local.php $backends['ldap']['logout'] => true I am redirected to the login page and see an error "Bind failed: Invalid credentials". With logout => false my URL stays at /passwd/ and I see "Mail server denied authentication". In all cases I can easily FIX this by clearing out my cookies for this domain and reloading the URL...then I get the proper login form. There is no problem if I logout manually. I could be wrong, but in the attached file with more details it looks like the bind fails in both cases (logout => true\|false) because it tried to bind with my old password. Again, I do not know the code well enough yet to suggest if this is a potential cause or just a symptom of the problem.