[Tickets #10617] Re: INGO Auth Generation Incorrect

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/10617
------------------------------------------------------------------------------
  Ticket             | 10617
  Updated By         | Jan Schneider <jan at horde.org>
  Summary            | INGO Auth Generation Incorrect
  Queue              | Ingo
  Version            | 2.0.5
  Type               | Bug
-State              | Unconfirmed
+State              | Feedback
-Priority           | 3. High
+Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             |
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2011-10-10 18:54) wrote:

> When trying to setup Ingo with my Dovecot Managesieve server I ran  
> into an authentication issue.  Ingo was always including the Horde  
> user credential when generating the base64 encoded plain  
> authentication as the first field.  I need this field to be blank in  
> order for Dovecot to properly authenticate.

I don't follow. What are you talking about?

> I tracked the issue down to a line in  
> ingo/lib/Transport/Timsievd.php. I went ahead an updated the file so  
> it will use the "euser" parameter passed from backends.php or  
> default to using the pre-existing call to Ingo::getUser(false).  I  
> have attached a patch detailing the updates I made.

That doesn't make sense, how is managesieve supposed to know for which  
user to accept the uploaded script, if you hardcode the effective user  
to a fixed value?