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

bugs@bugs.horde.org bugs at bugs.horde.org
Wed Jul 5 18:43:42 PDT 2006


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

Ticket URL: http://bugs.horde.org/ticket/?id=4119
-----------------------------------------------------------------------
 Ticket             | 4119
 Created By         | mzizka at hotmail.com
 Summary            | "Internal" Kolab users can't see account information
 Queue              | Horde Base
 Version            | HEAD
 State              | Unconfirmed
 Priority           | 1. Low
 Type               | Bug
 Owners             | 
+New Attachment     | account-info-kolab.patch
-----------------------------------------------------------------------


mzizka at hotmail.com (2006-07-05 18:43) wrote:

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.




More information about the bugs mailing list