[Tickets #6903] Re: Silence warning on creation/update of a Kolab object

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/6903
------------------------------------------------------------------------------
  Ticket             | 6903
  Updated By         | Gunnar Wrobel <p at rdus.de>
  Summary            | Silence warning on creation/update of a Kolab object
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Gunnar Wrobel
------------------------------------------------------------------------------


Gunnar Wrobel <p at rdus.de> (2008-06-25 03:20) wrote:

Ups, somehow missed your response to this one. Sorry for the late reply...

>> This looks not okay to me.
>>
>> Auth::getAuth() will usually resolve to something like wrobel at example.org.
>
> Oh, Auth::getAuth() always returns just the username for me. If it
> returns a complete email address, then my patch needs some tweaking.
> It happens for all users IIRC.
>
> Auth::getAuth() is defined as "user id". I'm not sure if it always
> must contain an @domain part.
>

Are you using the Auth::kolab driver then? The kolab driver should  
rewrite the user id to the primary mail adress (see the setAuth()  
function in that driver). It looks like you are using UIDs in your  
system. At least in former times that was problematic for other Horde  
subsystems and that is why the kolab driver does the rewrite. I admit  
I don't remember exactly what the effects of using a UID were. But my  
gut feeling is that even with our new infrastructure it makes more  
sense to use the primary Kolab ID.