[Tickets #4119] "Internal" Kolab users can't see account information
bugs@bugs.horde.org
bugs at bugs.horde.org
Thu Jul 6 05:45:19 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
Updated By | mzizka at hotmail.com
Summary | "Internal" Kolab users can't see account information
Queue | Kolab
State | Feedback
Priority | 1. Low
Type | Bug
Owners |
-----------------------------------------------------------------------
mzizka at hotmail.com (2006-07-06 05:45) wrote:
> 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.)
More information about the bugs
mailing list