Tickets :: [#4119] "Internal" Kolab users can't see account information

6.0.0-beta1

7/29/25

Summary	"Internal" Kolab users can't see account information
Queue	Kolab
Type	Bug
State	Resolved
Priority	1. Low
Owners
Requester	mzizka (at) hotmail (dot) com
Created	07/06/2006 (6963 days ago)
Due
Updated	08/18/2006 (6920 days ago)
Assigned	07/06/2006 (6963 days ago)
Resolved	08/18/2006 (6920 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

08/18/2006 01:46:54 PM	Jan Schneider	Comment #8 State ⇒ Resolved	Reply to this comment
Committed thanks.

08/18/2006 01:04:19 PM	Jan Schneider	Deleted Original Message

08/15/2006 01:29:32 PM	mzizka (at) hotmail (dot) com	Comment #7 New Attachment: account-info-kolab-internal.patch	Reply to this comment
Here's an updated patch set against current HEAD. You can remove the previous patch.

08/05/2006 01:24:13 AM	mzizka (at) hotmail (dot) com	Comment #6	Reply to this comment
Eventually :) Sorry, just been very busy, and still am. In a week or so I should have more time to look at this.

08/04/2006 10:14:58 PM	Jan Schneider	Comment #5	Reply to this comment
Are you going to update your patch?

07/06/2006 12:45:19 PM	mzizka (at) hotmail (dot) com	Comment #4	Reply to this comment
The phpdn setting is optional, you should take that into account. _ldapBind() would be a better method name IMO. Beside that, looks good. Over here I've actually removed the other bind setting (binddn) and have changed the code to only use the phpdn one everywhere (even for binds that used to be anonymous, so for instance internal users can also change their passwords with the passwd module). I don't think there's any need for Horde to have manager access, unless we want to manage users, which for now we can't. (And if we want to, it sure be a separate and clearly labeled setting.) Limited testing playing with the global address book in Turba with the manager access showed it to be unstable. For instance it truncates the list of email aliases. (Though I've not tried the HEAD revision.)

07/06/2006 07:33:06 AM	Jan Schneider	Comment #3 State ⇒ Feedback	Reply to this comment
The phpdn setting is optional, you should take that into account. _ldapBind() would be a better method name IMO. Beside that, looks good.

07/06/2006 03:09:07 AM	Chuck Hagenbuch	Version ⇒ Queue ⇒ Kolab

07/06/2006 03:07:57 AM	Chuck Hagenbuch	Deleted Original Message

07/06/2006 01:55:45 AM	mzizka (at) hotmail (dot) com	Comment #2 New Attachment: account-info-kolab-new.patch	Reply to this comment
Hmm I got all caught up in my symbolic links. Here's a patch that should work. Ditch the other one.

07/06/2006 01:43:42 AM	mzizka (at) hotmail (dot) com	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ "Internal" Kolab users can't see account information Queue ⇒ Horde Base New Attachment: account-info-kolab.patch State ⇒ Unconfirmed	Reply to this comment
The account information portal block is hard to get working properly with Kolab when using its LDAP driver. This patch addresses three proplems I encountered: 1) If you enable Kolab integration, it's not worth repeating the whole LDAP configuration again just for this portal block. So I added a driver which uses the Kolab configuration. 2) The LDAP driver binds anonymously, so special "internal" users in Kolab will only see an error message because they cannot be seen when binding anonyomously. Using this driver, the bind will use the Kolab's pseudo-anonymous "nobody" user, or whichever was set in "phpdn" (see ~~#4049~~). 3) When searching for the user entry, the LDAP systematically uses the username stripped of any domain name. This was a problem for me since I use the "mail" attribute for searching. I added an option on the Kolab driver (probably should be added to the LDAP driver as well, but I don't use that). Critical comments welcome, as this is my first patch.