| Summary | Special kolab user types cannot save their preferences |
| Queue | Kolab |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | |
| Requester | wrobel (at) gentoo (dot) org |
| Created | 06/16/2006 (6961 days ago) |
| Due | |
| Updated | 06/21/2006 (6956 days ago) |
| Assigned | 06/21/2006 (6956 days ago) |
| Resolved | 06/21/2006 (6956 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
like a standard user. The internal user is equivalent to a normal user
but the contact details of the user are not openly visible. Kontact
treats these accounts as equal also.
I don't know why the user for searching was named "nobody" but the
user is used for the same task in other php scripts of the kolab
project.
State ⇒ Feedback
these "special" user are really users that are supposed to login and
use the Kolab system, or are these maintenance/administration users?
New Attachment: package-horde.kolab-searchdn.patch
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Special kolab user types cannot save their preferences
Queue ⇒ Kolab
New Attachment: package-framework.kolab-searchdn.patch
State ⇒ Unconfirmed
section of the ldap tree that is not searchable by the anonymous user.
The Prefs ldap backend does support searching for the user dn, but it
does so as the anonymous user. Consequently the special user type will
not be able to save the horde preferences though they are able to log
into the system without problems.
Kolab provides a special user cn=nobody,cn=internal,... that also
allows searching for these special user types. I attached a suggested
patch that would extend the functionality of the ldap prefs backend to
allow setting a dn that will always be used for binding.