6.0.0-beta1
9/6/25

[#3695] kolab authentication, _username_hook_frombackend
Summary kolab authentication, _username_hook_frombackend
Queue Kolab
Type Bug
State Resolved
Priority 1. Low
Owners
Requester oliver (at) warpsix (dot) net
Created 03/26/2006 (7104 days ago)
Due
Updated 03/27/2006 (7103 days ago)
Assigned
Resolved 03/27/2006 (7103 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
03/27/2006 07:50:55 AM Jan Schneider Comment #3
State ⇒ Resolved
Reply to this comment
Fixed.
03/27/2006 07:44:47 AM tokoe (at) kde (dot) org Comment #2 Reply to this comment
Yes, that seems to be a bug indeed.

Jan, can you commit the fix?



Ciao,

Tobias


03/26/2006 09:55:35 PM oliver (at) warpsix (dot) net Comment #1
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ kolab authentication, _username_hook_frombackend
Queue ⇒ Kolab
Reply to this comment
today I stumbled over a line in horde/config/hooks.php, which looks 
like a bug to me:



hooks.php (FRAMEWORK_3 branch) says in function 
_username_hook_frombackend($userID):



             $result = ldap_search(

                 $ds,

                 $GLOBALS['conf']['kolab']['ldap']['basedn'],

                 "uid=$username"

             );



although the username is given to this function as $userID rather than 
$username.

That doesn't obviosly break anything but only the userID will be 
returned instead of

the corresponding email address from ldap. This breaks the kolab 
functionality if

users login with their uid instead of their email address.

So I changed the line (line #982 in my case) from

"uid=$username"



to



"uid=$userID"



Which seems to work well -  at least for me.



BTW:

this is my first post to this buglist - please tell me if I did 
something wrong of

missed some important details.



Oliver

Saved Queries