[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         | leena.heino at uta.fi
  Summary            | inconsistent authentication id usage within the
                     | activesync
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


leena.heino at uta.fi (2013-10-02 11:03) wrote:

> It seems this change might have broken authentication with  
> Activesync autoconfigure in some cases:  
> d048b5a83c04ec489b15fbbcfa2a8cd354a1d384
>
> Previously Autosync autoconfigure in horde always seemed to use only  
> the username to authenticate to the activesync / mail server server,  
> but after this or perhaps some other change in the activesync code  
> it now seems to use both the username and the email address for  
> authentication.
>
> Would it be possible to revert this change or modify the code so  
> that activesync driver consistently uses username to authenticate to  
> activesync server?

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.

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