Tickets :: Comment on [#8270] Wicked tries (and fails) to bind to LDAP as Page creator

* Your Email Address
* Spam protection	Enter the letters below: .__ . ..__.. .__. [__)\| \|\| \|\| \| \| \| \\|/\\|\|__\|\|___\|__\
Comment	> Setup: Horde 3.3.4-RC1, Wicked 1.0-cvs. > > > > When accessing a page in Wicked that has been created by another > user, Wicked makes a call to LDAP and tries to bind as the page > author. The first time after logging on that this occurs results in > an error: "The preferences backend is currently unavailable and your > preferences have not been loaded. You may continue to use the system > with default settings." > > > > LDAP log: > > > > May 14 00:47:55 server01 slapd[1156]: conn=113175 op=2 BIND > dn="uid=simon,ou=users,dc=simonandkate,dc=lan" method=128 > > May 14 00:47:55 server01 slapd[1156]: conn=113175 op=2 RESULT tag=97 > err=53 text=unauthenticated bind (DN with no password) disallowed > > > > On subsequent page accesses the error is still logged by LDAP, but > the error message in Horde appears to be suppressed. > > > > This appears to be occurring across several of the Horde apps, see > other bug tickets logged over last few weeks - 8269, 8251, 8246, > 7418. Jan I notice has commented in a couple of them (in the > Kronolith and Nag tickets) as to the user being called not > necessarily being the current user. It would appear there is a basic > setup issue with the way I (and at least one other) am using LDAP and > the Horde code. > > > > I am happy to provide details of my LDAP setup if it will help anyone > debugging why Horde is trying to do this.
Attachment
Watch this ticket

Saved Queries