Summary | inconsistent authentication id usage within the activesync |
Queue | Horde Framework Packages |
Queue Version | Git master |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | mrubinsk (at) horde (dot) org |
Requester | leena.heino (at) uta (dot) fi |
Created | 10/02/2013 (4296 days ago) |
Due | |
Updated | 10/02/2013 (4296 days ago) |
Assigned | 10/02/2013 (4296 days ago) |
Resolved | 10/02/2013 (4296 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
State ⇒ Resolved
It was actually due to clients not sending http authentication data on
the initial AutoDiscover request. Should be fixed now.
Assigned to Michael Rubinsky
State ⇒ Feedback
usage is correct. Even with correct authentication id the
authentication still seems to fail in some cases.
Horde_Activesync::authenticate(), which is why it was removed from
Horde_ActiveSync_Request_Autodisocover::handle(), it was redundant.
sends a mangled or broken password to the authenticating activesync
/ mail server?
user and password are that are being passed around, I can't reproduce
this.
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?
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ inconsistent authentication id usage within the activesync
Queue ⇒ Horde Framework Packages
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
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?