[Tickets #12731] Re: inconsistent authentication id usage within the activesync

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12731
------------------------------------------------------------------------------
  Ticket             | 12731
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | inconsistent authentication id usage within the
                     | activesync
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
-State              | Unconfirmed
+State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2013-10-02 13:11) wrote:

> For testing I reverted the change and now the authentication id  
> usage is correct. Even with correct authentication id the  
> authentication still seems to fail in some cases.

This is incorrect. The email -> user_id mapping is attempted in  
Horde_Activesync::authenticate(), which is why it was removed from  
Horde_ActiveSync_Request_Autodisocover::handle(), it was redundant.

> Could it be possible that the activesync driver in horde sometimes  
> sends a mangled or broken password to the authenticating activesync  
> / mail server?

You are going to need to debug this and figure out what the values for  
user and password are that are being passed around, I can't reproduce  
this.